removed autogenerated munge analytics from files

kubernetes · Nov 3, 2017 · a6dcf86 · a6dcf86
1 parent b41c258
commit a6dcf86
Show file tree

Hide file tree

Showing 171 changed files with 1 addition and 764 deletions.
diff --git a/contributors/design-proposals/README.md b/contributors/design-proposals/README.md
@@ -9,7 +9,3 @@ Note that a number of these documents are historical and may be out of date or u
 TODO: Add the current status to each document and clearly indicate which are up to date.
 
 TODO: Document the [proposal process](../devel/faster_reviews.md#1-dont-build-a-cathedral-in-one-pr).
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/README.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/admission_control.md b/contributors/design-proposals/api-machinery/admission_control.md
@@ -99,8 +99,3 @@ following:
    - If operation=connect, exec
 
 If at any step, there is an error, the request is canceled.
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/admission_control.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/admission_control_extension.md b/contributors/design-proposals/api-machinery/admission_control_extension.md
@@ -632,9 +632,4 @@ Some options:
 
 It should be easy for a novice Kubernetes administrator to apply simple policy rules to the cluster. In
 the future it is desirable to have many such policy engines enabled via extension to enable quick policy 
-customization to meet specific needs.
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/admission_control_extension.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
+customization to meet specific needs.
diff --git a/contributors/design-proposals/api-machinery/aggregated-api-servers.md b/contributors/design-proposals/api-machinery/aggregated-api-servers.md
@@ -268,8 +268,3 @@ There were other alternatives that we had discussed.
   providing a centralised authentication and authorization service which all of
   the servers can use.
 
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/aggregated-api-servers.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/api-chunking.md b/contributors/design-proposals/api-machinery/api-chunking.md
@@ -175,8 +175,3 @@ The initial chunking implementation would focus on consistent listing on server
 For the initial alpha release, chunking would be behind a feature flag and attempts to provide the `continue` or `limit` flags should be ignored. While disabled, a `continue` token should never be returned by the server as part of a list.
 
 Future work might offer more options for clients to page in an inconsistent fashion, or allow clients to directly specify the parts of the namespace / name keyspace they wish to range over (paging).
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/server-get.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/api-group.md b/contributors/design-proposals/api-machinery/api-group.md
@@ -113,7 +113,3 @@ To expose a list of the supported Openshift groups to clients, OpenShift just ha
 ## Future work
 
 1. Dependencies between groups: we need an interface to register the dependencies between groups. It is not our priority now as the use cases are not clear yet.
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/api-group.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/apiserver-watch.md b/contributors/design-proposals/api-machinery/apiserver-watch.md
@@ -137,8 +137,3 @@ the same time, we can introduce an additional etcd event type: EtcdResync
   However, this might turn out to be unnecessary optimization if apiserver
   will always keep up (which is possible in the new design). We will work
   out all necessary details at that point.
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/apiserver-watch.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/auditing.md b/contributors/design-proposals/api-machinery/auditing.md
@@ -374,7 +374,3 @@ Below are the possible future extensions to the auditing mechanism:
 * Define how filters work. They should enable dropping sensitive fields from the request/response/storage objects.
 * Allow setting a unique identifier which allows matching audit events across apiserver and federated servers.
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/sysctl.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/client-package-structure.md b/contributors/design-proposals/api-machinery/client-package-structure.md
@@ -307,7 +307,3 @@ that client will not have to change their code until they are deliberately
 upgrading their import. We probably will want to generate some sort of stub test
 with a clientset, to ensure that we don't change the interface.
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/client-package-structure.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/controller-ref.md b/contributors/design-proposals/api-machinery/controller-ref.md
@@ -415,7 +415,3 @@ Summary of significant revisions to this document:
     * Specify ControllerRef-related behavior changes upon upgrade/downgrade.
   * [Implementation](#implementation)
     * List all work to be done and mark items already completed as of this edit.
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/controller-ref.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/event_compression.md b/contributors/design-proposals/api-machinery/event_compression.md
@@ -162,8 +162,3 @@ compressing multiple recurring events in to a single event.
 single event to optimize etcd storage.
  * PR [#4444](http://pr.k8s.io/4444): Switch events history to use LRU cache
 instead of map.
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/event_compression.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/extending-api.md b/contributors/design-proposals/api-machinery/extending-api.md
@@ -196,8 +196,3 @@ Thus, listing a third-party resource can be achieved by listing the directory:
 ```
 ${standard-k8s-prefix}/third-party-resources/${third-party-resource-namespace}/${third-party-resource-name}/${resource-namespace}/
 ```
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/extending-api.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/garbage-collection.md b/contributors/design-proposals/api-machinery/garbage-collection.md
@@ -349,9 +349,3 @@ In case the garbage collector is mistakenly deleting objects, we should provide
     * Before an object is deleted from the registry, the API server clears fields like DeletionTimestamp, then creates the object in /archive and sets a TTL.
     * Add a `kubectl restore` command, which takes a resource/name pair as input, creates the object with the spec stored in the /archive, and deletes the archived object.
 
-
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/garbage-collection.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/metadata-policy.md b/contributors/design-proposals/api-machinery/metadata-policy.md
@@ -130,8 +130,3 @@ single scheduler, as opposed to choosing a scheduler, a desire mentioned in
 `MetadataPolicy` could be used. Issue #17324 proposes to create a generalized
 API for matching "claims" to "service classes"; matching a pod to a scheduler
 would be one use for such an API.
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/metadata-policy.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/protobuf.md b/contributors/design-proposals/api-machinery/protobuf.md
@@ -473,8 +473,3 @@ The generated protobuf will be checked with a verify script before merging.
 ## Open Questions
 
 * Is supporting stored protobuf files on disk in the kubectl client worth it?
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/protobuf.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/server-get.md b/contributors/design-proposals/api-machinery/server-get.md
@@ -177,7 +177,3 @@ fall back to client side functions.
 Server side code would reuse the existing display functions but replace TabWriter with either a structured writer
 or the tabular form.
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/server-get.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md b/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md
@@ -167,7 +167,3 @@ To make the new kubectl compatible with the 1.4 and earlier masters, kubectl nee
 1.4 `kubectl delete rc/rs` uses `DeleteOptions.OrphanDependents=true`, which is going to be converted to `DeletePropagationBackground` (see [API Design](#api-changes)) by a 1.5 master, so its behavior keeps the same.
 
 Pre 1.4 `kubectl delete` uses `DeleteOptions.OrphanDependents=nil`, so does the 1.4 `kubectl delete` for resources other than rc and rs. The option is going to be converted to `DeletePropagationDefault` (see [API Design](#api-changes)) by a 1.5 master, so these commands behave the same as when working with a 1.4 master.
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/synchronous-garbage-collection.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/apps/OBSOLETE_templates.md b/contributors/design-proposals/apps/OBSOLETE_templates.md
@@ -562,8 +562,3 @@ Openshift handles template processing via a server endpoint which consumes a tem
 produced by processing the template.  It is also possible to handle the entire template processing flow via the client, but this was deemed
 undesirable as it would force each client tool to reimplement template processing (e.g. the standard CLI tool, an eclipse plugin, a plugin for a CI system like Jenkins, etc).  The assumption in this proposal is that server side template processing is the preferred implementation approach for
 this reason.
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/templates.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/apps/cronjob.md b/contributors/design-proposals/apps/cronjob.md
@@ -333,7 +333,3 @@ Below are the possible future extensions to the Job controller:
   happening in [#18827](https://issues.k8s.io/18827).
 * Be able to specify more general template in `.spec` field, to create arbitrary
   types of resources. This relates to the work happening in [#18215](https://issues.k8s.io/18215).
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/cronjob.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/apps/daemon.md b/contributors/design-proposals/apps/daemon.md
@@ -201,7 +201,3 @@ restartPolicy set to Always.
 
 - Should work similarly to [Deployment](http://issues.k8s.io/1743).
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/daemon.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/apps/deploy.md b/contributors/design-proposals/apps/deploy.md
@@ -138,7 +138,3 @@ Users sometimes need to temporarily disable a deployment. See issue [#14516](htt
 ### Perm-failed Deployments
 
 The deployment could be marked as "permanently failed" for a given spec hash so that the system won't continue thrashing on a doomed deployment. The users can retry a failed deployment with `kubectl rollout retry`. See issue [#14519](https://github.com/kubernetes/kubernetes/issues/14519).
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/deploy.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/apps/deployment.md b/contributors/design-proposals/apps/deployment.md
@@ -257,8 +257,3 @@ Apart from the above, we want to add support for the following:
 
 - https://github.com/kubernetes/kubernetes/issues/1743 has most of the
   discussion that resulted in this proposal.
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/deployment.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/apps/indexed-job.md b/contributors/design-proposals/apps/indexed-job.md
@@ -894,7 +894,3 @@ is verbose.  For StatefulSet, this is less of a problem.
 This differs from StatefulSet in that StatefulSet uses names and not indexes. StatefulSet is
 intended to support ones to tens of things.
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/indexed-job.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/apps/job.md b/contributors/design-proposals/apps/job.md
@@ -206,7 +206,3 @@ Below are the possible future extensions to the Job controller:
   by providing pointers to Pods in the JobStatus ([see comment](https://github.com/kubernetes/kubernetes/pull/11746/files#r37142628)).
 * help users avoid non-unique label selectors ([see this proposal](../../docs/design/selector-generation.md))
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/job.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/apps/selector-generation.md b/contributors/design-proposals/apps/selector-generation.md
@@ -174,7 +174,3 @@ Docs will be edited to show examples without a `job.spec.selector`.
 We probably want as much as possible the same behavior for Job and
 ReplicationController.
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/selector-generation.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/apps/stateful-apps.md b/contributors/design-proposals/apps/stateful-apps.md
@@ -355,9 +355,3 @@ Requested features:
 
 StatefulSets were formerly known as PetSets and were renamed to be less "cutesy" and more descriptive as a
 prerequisite to moving to beta. No animals were harmed in the making of this proposal.
-
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/stateful-apps.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/architecture/architecture.md b/contributors/design-proposals/architecture/architecture.md
@@ -246,7 +246,3 @@ itself:
 A single Kubernetes cluster may span multiple availability zones.
 
 However, for the highest availability, we recommend using [cluster federation](../multicluster/federation.md).
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/architecture.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/architecture/identifiers.md b/contributors/design-proposals/architecture/identifiers.md
@@ -107,7 +107,3 @@ from whence it came.
 unique across time.
       1. This may correspond to Docker's container ID.
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/identifiers.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/architecture/namespaces.md b/contributors/design-proposals/architecture/namespaces.md
@@ -363,8 +363,3 @@ storage.
 
 At this point, all content associated with that Namespace, and the Namespace
 itself are gone.
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/namespaces.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/architecture/principles.md b/contributors/design-proposals/architecture/principles.md
@@ -96,7 +96,3 @@ TODO
 
 * [Eric Raymond's 17 UNIX rules](https://en.wikipedia.org/wiki/Unix_philosophy#Eric_Raymond.E2.80.99s_17_Unix_Rules)
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/principles.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/auth/access.md b/contributors/design-proposals/auth/access.md
@@ -370,7 +370,3 @@ Improvements:
 - Policies to drop logging for high rate trusted API calls, or by users
 performing audit or other sensitive functions.
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/access.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/auth/apparmor.md b/contributors/design-proposals/auth/apparmor.md
@@ -300,7 +300,3 @@ documentation for following this process in a Kubernetes environment.
   ```
   $ apparmor_parser --remove /path/to/profile
   ```
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/apparmor.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/auth/enhance-pluggable-policy.md b/contributors/design-proposals/auth/enhance-pluggable-policy.md
@@ -422,8 +422,3 @@ type LocalResourceAccessReviewResponse struct {
   Groups []string
 }
 ```
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/enhance-pluggable-policy.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/auth/image-provenance.md b/contributors/design-proposals/auth/image-provenance.md
@@ -324,8 +324,3 @@ Additionally, just sending all the fields of just the Pod kind also has problems
 - because we do not know which fields of an object are inspected by the backend, caching of decisions is not effective. Sending fewer fields allows caching.
 - sending fewer fields makes it possible to rev the version of the webhook request slower than the version of our internal objects (e.g. pod v2 could still use imageReview v1.)
 probably lots more reasons.
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/image-provenance.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/auth/pod-security-context.md b/contributors/design-proposals/auth/pod-security-context.md
@@ -368,7 +368,3 @@ E2E test cases will be added to test the correct determination of the security c
 1.  The Kubelet will use the new fields on the `PodSecurityContext` for host namespace control
 2.  The Kubelet will be modified to correctly implement the backward compatibility and effective
     security context determination defined here
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/pod-security-context.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/auth/secrets.md b/contributors/design-proposals/auth/secrets.md
@@ -622,7 +622,3 @@ on their filesystems:
     /etc/secret-volume/username
     /etc/secret-volume/password
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/secrets.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/auth/security.md b/contributors/design-proposals/auth/security.md
@@ -212,7 +212,3 @@ a separate component that can delete bindings but not create them). The
 scheduler may need read access to user or project-container information to
 determine preferential location (underspecified at this time).
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/security.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/auth/security_context.md b/contributors/design-proposals/auth/security_context.md
@@ -186,7 +186,3 @@ privileged. Contexts that attempt to define a UID or SELinux options will be
 denied by default. In the future the admission plugin will base this decision
 upon configurable policies that reside within the [service account](http://pr.k8s.io/2297).
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/security_context.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/auth/service_accounts.md b/contributors/design-proposals/auth/service_accounts.md
@@ -204,7 +204,3 @@ Finally, it may provide an interface to automate creation of new
 serviceAccounts. In that case, the user may want to GET serviceAccounts to see
 what has been created.
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/service_accounts.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md b/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md
@@ -254,10 +254,3 @@ autoscaler to create a new pod.  Discussed in issue [#3247](https://github.com/k
 * *[future]* **When scaling down, make more educated decision which pods to
 kill.** E.g.: if two or more pods from the same replication controller are on
 the same node, kill one of them. Discussed in issue [#4301](https://github.com/kubernetes/kubernetes/issues/4301).
-
-
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/horizontal-pod-autoscaler.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/autoscaling/hpa-v2.md b/contributors/design-proposals/autoscaling/hpa-v2.md
@@ -285,7 +285,3 @@ come from the [custom metrics API](custom-metrics-api.md), which is
 an adapter API which sources metrics directly from the monitoring
 pipeline.
 
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/hpa-v2.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/autoscaling/initial-resources.md b/contributors/design-proposals/autoscaling/initial-resources.md
@@ -70,6 +70,3 @@ and should be introduced shortly after the first version is done:
 * add estimation as annotations for those containers that already has resources set
 * support for other data sources like [Hawkular](http://www.hawkular.org/)
 
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/proposals/initial-resources.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->
diff --git a/contributors/design-proposals/aws/aws_under_the_hood.md b/contributors/design-proposals/aws/aws_under_the_hood.md
@@ -303,8 +303,3 @@ These scripts are responsible for mounting and formatting volumes, downloading
 Salt and Kubernetes from the S3 bucket, and then triggering Salt to actually
 install Kubernetes.
 
-
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/design/aws_under_the_hood.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->