diff --git a/cassandra/java/README.md b/cassandra/java/README.md index 2713c539..373fa9fa 100644 --- a/cassandra/java/README.md +++ b/cassandra/java/README.md @@ -28,7 +28,3 @@ expand this capability. This in affect makes every node a seed provider, which is not a recommended best practice. This increases maintenance and reduces gossip performance. - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storage/cassandra/java/README.md?pixel)]() - diff --git a/guestbook-go/README.md b/guestbook-go/README.md index fc0c366b..5e086634 100644 --- a/guestbook-go/README.md +++ b/guestbook-go/README.md @@ -265,7 +265,3 @@ redis-replica Tip: To turn down your Kubernetes cluster, follow the corresponding instructions in the version of the [Getting Started Guides](https://kubernetes.io/docs/getting-started-guides/) that you previously used to create your cluster. - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/guestbook-go/README.md?pixel)]() - diff --git a/guidelines.md b/guidelines.md index ff66e89d..ce46b03f 100644 --- a/guidelines.md +++ b/guidelines.md @@ -137,8 +137,3 @@ Each example must be well-structured and documented to ensure clarity and usabil potential incompatibility with current Kubernetes versions. * Community Maintenance: SIG Apps will act as the overall steward, and individual example maintainers (original authors or new volunteers) are crucial for the health of the repository. - - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/guidelines.md?pixel)]() - diff --git a/mysql-cinder-pd/README.md b/mysql-cinder-pd/README.md index c0342ca9..04476772 100644 --- a/mysql-cinder-pd/README.md +++ b/mysql-cinder-pd/README.md @@ -45,7 +45,3 @@ This should now 3. Mount it on the kubelet's host machine 4. Spin up a container with this volume mounted to the path specified in the pod definition - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/mysql-cinder-pd/README.md?pixel)]() - diff --git a/staging/cluster-dns/README.md b/staging/cluster-dns/README.md index a33a85c0..8d75743b 100644 --- a/staging/cluster-dns/README.md +++ b/staging/cluster-dns/README.md @@ -180,7 +180,3 @@ kubectl create -f examples/staging/cluster-dns/dns-frontend-pod.yaml kubectl logs dns-frontend ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/cluster-dns/README.md?pixel)]() - diff --git a/staging/cockroachdb/README.md b/staging/cockroachdb/README.md index 015939ff..d9b99933 100644 --- a/staging/cockroachdb/README.md +++ b/staging/cockroachdb/README.md @@ -119,7 +119,3 @@ we can clean up everything that we created in one quick command using a selector kubectl delete statefulsets,persistentvolumes,persistentvolumeclaims,services,poddisruptionbudget -l app=cockroachdb ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/cockroachdb/README.md?pixel)]() - diff --git a/staging/elasticsearch/README.md b/staging/elasticsearch/README.md index 79b229b4..c0414d05 100644 --- a/staging/elasticsearch/README.md +++ b/staging/elasticsearch/README.md @@ -189,6 +189,3 @@ You should see something similar to the following: } ``` - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/elasticsearch/README.md?pixel)]() - diff --git a/staging/elasticsearch/production_cluster/README.md b/staging/elasticsearch/production_cluster/README.md index c2551358..9767e4e8 100644 --- a/staging/elasticsearch/production_cluster/README.md +++ b/staging/elasticsearch/production_cluster/README.md @@ -190,7 +190,3 @@ You should see something similar to the following: } ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/elasticsearch/production_cluster/README.md?pixel)]() - diff --git a/staging/explorer/README.md b/staging/explorer/README.md index 3e2dba2a..cb1b03a4 100644 --- a/staging/explorer/README.md +++ b/staging/explorer/README.md @@ -127,7 +127,3 @@ Error: <*>lookup elasticsearch-logging: no such host ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/explorer/README.md?pixel)]() - diff --git a/staging/https-nginx/README.md b/staging/https-nginx/README.md index 09f82789..ba560c09 100644 --- a/staging/https-nginx/README.md +++ b/staging/https-nginx/README.md @@ -124,6 +124,3 @@ $ curl https://104.198.1.26:30028 -k For more information on how to run this in a kubernetes cluster, please see the [user-guide](https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/). - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/https-nginx/README.md?pixel)]() - diff --git a/staging/javaee/README.md b/staging/javaee/README.md index 2929b503..3b6a51a9 100644 --- a/staging/javaee/README.md +++ b/staging/javaee/README.md @@ -128,7 +128,3 @@ kubectl delete -f examples/javaee/mysql-service.yaml kubectl delete -f examples/javaee/wildfly-rc.yaml ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/javaee/README.md?pixel)]() - diff --git a/staging/javaweb-tomcat-sidecar/README.md b/staging/javaweb-tomcat-sidecar/README.md index 2788a024..7bbdfaf1 100644 --- a/staging/javaweb-tomcat-sidecar/README.md +++ b/staging/javaweb-tomcat-sidecar/README.md @@ -177,8 +177,3 @@ All resources created in this application can be deleted: $ kubectl delete -f examples/javaweb-tomcat-sidecar/javaweb-2.yaml ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/javaweb-tomcat-sidecar/README.md?pixel)]() - - diff --git a/staging/job/expansions/README.md b/staging/job/expansions/README.md index ea72d566..0e8f4349 100644 --- a/staging/job/expansions/README.md +++ b/staging/job/expansions/README.md @@ -1,7 +1,3 @@ This file has moved to: http://kubernetes.io/docs/user-guide/jobs/ - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/job/expansions/README.md?pixel)]() - diff --git a/staging/job/work-queue-1/README.md b/staging/job/work-queue-1/README.md index d32d130f..0e8f4349 100644 --- a/staging/job/work-queue-1/README.md +++ b/staging/job/work-queue-1/README.md @@ -1,7 +1,3 @@ This file has moved to: http://kubernetes.io/docs/user-guide/jobs/ - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/job/work-queue-1/README.md?pixel)]() - diff --git a/staging/job/work-queue-2/README.md b/staging/job/work-queue-2/README.md index 94355c0f..0e8f4349 100644 --- a/staging/job/work-queue-2/README.md +++ b/staging/job/work-queue-2/README.md @@ -1,7 +1,3 @@ This file has moved to: http://kubernetes.io/docs/user-guide/jobs/ - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/job/work-queue-2/README.md?pixel)]() - diff --git a/staging/meteor/README.md b/staging/meteor/README.md index 4281a618..cdd2de69 100644 --- a/staging/meteor/README.md +++ b/staging/meteor/README.md @@ -209,7 +209,3 @@ container section: ], ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/meteor/README.md?pixel)]() - diff --git a/staging/meteor/dockerbase/README.md b/staging/meteor/dockerbase/README.md index 2c04dff7..3b8a81f4 100644 --- a/staging/meteor/dockerbase/README.md +++ b/staging/meteor/dockerbase/README.md @@ -8,7 +8,3 @@ To build and push the base meteor-kubernetes image: docker build -t chees/meteor-kubernetes . docker push chees/meteor-kubernetes - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/meteor/dockerbase/README.md?pixel)]() - diff --git a/staging/newrelic-infrastructure/README.md b/staging/newrelic-infrastructure/README.md index 6bd0a8c7..efb818b8 100644 --- a/staging/newrelic-infrastructure/README.md +++ b/staging/newrelic-infrastructure/README.md @@ -141,6 +141,3 @@ The daemonset instructs Kubernetes to spawn pods on each node, mapping /dev/, /r It's a bit cludgy to define the environment variables like we do here in these config files. There is [another issue](https://github.com/kubernetes/kubernetes/issues/4710) to discuss adding mapping secrets to environment variables in Kubernetes. (Personally I don't like that method and prefer to use the config secrets.) - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/newrelic/README.md?pixel)]() - diff --git a/staging/newrelic/README.md b/staging/newrelic/README.md index bc1babe4..45f067ab 100644 --- a/staging/newrelic/README.md +++ b/staging/newrelic/README.md @@ -155,6 +155,3 @@ When the New Relic agent starts, `NRSYSMOND_hostname` is set using the output of It's a bit cludgy to define the environment variables like we do here in these config files. There is [another issue](https://github.com/kubernetes/kubernetes/issues/4710) to discuss adding mapping secrets to environment variables in Kubernetes. - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/newrelic/README.md?pixel)]() - diff --git a/staging/nodesjs-mongodb/README.md b/staging/nodesjs-mongodb/README.md index 3208bf51..041c6a13 100644 --- a/staging/nodesjs-mongodb/README.md +++ b/staging/nodesjs-mongodb/README.md @@ -277,6 +277,3 @@ With Google Cloud Platform, get the IP address of all load balancers with the fo gcloud compute forwarding-rules list ``` - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/nodesjs-mongodb/README.md?pixel)]() - diff --git a/staging/openshift-origin/README.md b/staging/openshift-origin/README.md index 34b24351..1525a52e 100644 --- a/staging/openshift-origin/README.md +++ b/staging/openshift-origin/README.md @@ -205,7 +205,3 @@ Clean up your cluster from resources created with this example: $ ${OPENSHIFT_EXAMPLE}/cleanup.sh ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/openshift-origin/README.md?pixel)]() - diff --git a/staging/persistent-volume-provisioning/README.md b/staging/persistent-volume-provisioning/README.md index 815fdb86..ff559162 100644 --- a/staging/persistent-volume-provisioning/README.md +++ b/staging/persistent-volume-provisioning/README.md @@ -544,6 +544,3 @@ $ kubectl exec -it $PODNAME --namespace=myns -- df -h | grep rbd /dev/rbd1 2.9G 4.5M 2.8G 1% /var/lib/www/html ``` - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/persistent-volume-provisioning/README.md?pixel)]() - diff --git a/staging/phabricator/README.md b/staging/phabricator/README.md index 79a08a75..feb921e7 100644 --- a/staging/phabricator/README.md +++ b/staging/phabricator/README.md @@ -210,7 +210,3 @@ To turn down a Kubernetes cluster: $ cluster/kube-down.sh ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/phabricator/README.md?pixel)]() - diff --git a/staging/podsecuritypolicy/rbac/README.md b/staging/podsecuritypolicy/rbac/README.md index 6d528157..016dfee9 100644 --- a/staging/podsecuritypolicy/rbac/README.md +++ b/staging/podsecuritypolicy/rbac/README.md @@ -243,6 +243,3 @@ $ kubectl get pod nginx -o yaml | egrep "psp|privileged" privileged: true ``` - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/podsecuritypolicy/rbac/README.md?pixel)]() - diff --git a/staging/runtime-constraints/README.md b/staging/runtime-constraints/README.md index 82f6c0ee..9cf42df1 100644 --- a/staging/runtime-constraints/README.md +++ b/staging/runtime-constraints/README.md @@ -280,6 +280,3 @@ You see that our BestEffort pod goes in a restart cycle, but the pods with great As you can see, we rely on the Kernel to react to system OOM events. Depending on how your host operating system was configured, and which process the Kernel ultimately decides to kill on your Node, you may experience unstable results. In addition, during an OOM event, while the kernel is cleaning up processes, the system may experience significant periods of slow down or appear unresponsive. As a result, while the system allows you to overcommit on memory, we recommend to not induce a Kernel sys OOM. - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/runtime-constraints/README.md?pixel)]() - diff --git a/staging/selenium/README.md b/staging/selenium/README.md index 539d106e..21b41719 100644 --- a/staging/selenium/README.md +++ b/staging/selenium/README.md @@ -188,7 +188,3 @@ kubectl delete deployment selenium-python kubectl delete svc selenium-hub ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/selenium/README.md?pixel)]() - diff --git a/staging/sharing-clusters/README.md b/staging/sharing-clusters/README.md index 38f46fa0..1bda8c45 100644 --- a/staging/sharing-clusters/README.md +++ b/staging/sharing-clusters/README.md @@ -181,7 +181,3 @@ eu-node-loh2 kubernetes.io/hostname=eu-node-loh2 Ready For a more advanced example of sharing clusters, see the [service-loadbalancer](https://github.com/kubernetes/contrib/tree/master/service-loadbalancer/README.md) - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/sharing-clusters/README.md?pixel)]() - diff --git a/staging/simple-nginx.md b/staging/simple-nginx.md index 5d413ccf..f3aa5c84 100644 --- a/staging/simple-nginx.md +++ b/staging/simple-nginx.md @@ -68,7 +68,3 @@ kubectl delete deployment my-nginx Most people will eventually want to use declarative configuration files for creating/modifying their applications. A [simplified introduction](https://kubernetes.io/docs/user-journeys/users/application-developer/foundational/#section-2) is given in a different document. - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/simple-nginx.md?pixel)]() - diff --git a/staging/spark/README.md b/staging/spark/README.md index 5a0e17c8..9a4f2d32 100644 --- a/staging/spark/README.md +++ b/staging/spark/README.md @@ -371,6 +371,3 @@ Then visit [http://localhost:8080/](http://localhost:8080/). top right as well), the `port-forward` probably failed and needs to be restarted. See #12179. - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/spark/README.md?pixel)]() - diff --git a/staging/spark/spark-gluster/README.md b/staging/spark/spark-gluster/README.md index 348a64eb..bd572c5f 100644 --- a/staging/spark/spark-gluster/README.md +++ b/staging/spark/spark-gluster/README.md @@ -118,6 +118,3 @@ While still in the container, you can see the output of your Spark Job in the Di root@spark-master-controller-c1sqd:/# ls -l /mnt/glusterfs/output ``` - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/spark/spark-gluster/README.md?pixel)]() - diff --git a/staging/storage/hazelcast/README.md b/staging/storage/hazelcast/README.md index 3ff8fa08..381fb169 100644 --- a/staging/storage/hazelcast/README.md +++ b/staging/storage/hazelcast/README.md @@ -230,7 +230,3 @@ kubectl scale deployment hazelcast --replicas 4 See [here](https://github.com/pires/hazelcast-kubernetes-bootstrapper/blob/master/src/main/java/com/github/pires/hazelcast/HazelcastDiscoveryController.java) - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storage/hazelcast/README.md?pixel)]() - diff --git a/staging/storage/mysql-galera/README.md b/staging/storage/mysql-galera/README.md index a1489349..28107aa0 100644 --- a/staging/storage/mysql-galera/README.md +++ b/staging/storage/mysql-galera/README.md @@ -130,8 +130,3 @@ At this point, there is a working cluster that can begin being used via the pxc- This setup certainly can become more fluid and dynamic. One idea is to perhaps use an etcd container to store information about node state. Originally, there was a read-only kubernetes API available to each container but that has since been removed. Also, Kelsey Hightower is working on moving the functionality of confd to Kubernetes. This could replace the shell duct tape that builds the cluster configuration file for the image. - - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storage/mysql-galera/README.md?pixel)]() - diff --git a/staging/storage/redis/README.md b/staging/storage/redis/README.md index 7d324e51..ea5ca1ca 100644 --- a/staging/storage/redis/README.md +++ b/staging/storage/redis/README.md @@ -128,7 +128,3 @@ kubectl scale rc redis-sentinel --replicas=3 kubectl delete pods redis-master ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/storage/redis/README.md?pixel)]() - diff --git a/staging/storage/rethinkdb/README.md b/staging/storage/rethinkdb/README.md index 061854c4..81bad433 100644 --- a/staging/storage/rethinkdb/README.md +++ b/staging/storage/rethinkdb/README.md @@ -124,7 +124,3 @@ the generated pods which is using `nodeSelector` to force k8s to schedule contai * see [antmanler/rethinkdb-k8s](https://github.com/antmanler/rethinkdb-k8s) for detail - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storage/rethinkdb/README.md?pixel)]() - diff --git a/staging/storage/vitess/README.md b/staging/storage/vitess/README.md index 707f4c53..395e9709 100644 --- a/staging/storage/vitess/README.md +++ b/staging/storage/vitess/README.md @@ -107,7 +107,3 @@ in Vitess. Each page number is assigned to one of the shards using a You may also want to remove any firewall rules you created. - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storage/vitess/README.md?pixel)]() - diff --git a/staging/storm/README.md b/staging/storm/README.md index 217bba3c..63c9477c 100644 --- a/staging/storm/README.md +++ b/staging/storm/README.md @@ -166,7 +166,3 @@ Make sure the Nimbus Pod is running. ```kubectl create -f storm-worker-controller.yaml``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storm/README.md?pixel)]() - diff --git a/staging/sysdig-cloud/README.md b/staging/sysdig-cloud/README.md index 14d43150..11229f88 100644 --- a/staging/sysdig-cloud/README.md +++ b/staging/sysdig-cloud/README.md @@ -20,8 +20,3 @@ https://github.com/draios/sysdig-cloud-scripts/tree/master/agent_deploy/kubernet Please see the Sysdig Cloud support site for the latest documentation: http://support.sysdigcloud.com/hc/en-us/sections/200959909 - - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/sysdig-cloud/README.md?pixel)]() - diff --git a/staging/volumes/aws_ebs/README.md b/staging/volumes/aws_ebs/README.md index 654c4763..1e7cc50c 100644 --- a/staging/volumes/aws_ebs/README.md +++ b/staging/volumes/aws_ebs/README.md @@ -31,7 +31,3 @@ You should now be able to query your web server: $ Hello World ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/aws_ebs/README.md?pixel)]() - diff --git a/staging/volumes/azure_disk/README.md b/staging/volumes/azure_disk/README.md index 3ba0086b..630a2d12 100644 --- a/staging/volumes/azure_disk/README.md +++ b/staging/volumes/azure_disk/README.md @@ -18,6 +18,3 @@ Launch the Pod: # kubectl create -f examples/staging/volumes/azure_disk/azure.yaml ``` - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/volumes/azure_disk/README.md?pixel)]() - diff --git a/staging/volumes/azure_file/README.md b/staging/volumes/azure_file/README.md index 08157539..228fe48f 100644 --- a/staging/volumes/azure_file/README.md +++ b/staging/volumes/azure_file/README.md @@ -57,6 +57,3 @@ The same mechanism can also be used to mount the Azure File Storage using a Pers Correspondingly, you then mount the volume inside pods using the normal `persistentVolumeClaim` reference. This mechanism is used in the sample pod YAML [azure-2.yaml](azure-2.yaml). - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/azure_file/README.md?pixel)]() - diff --git a/staging/volumes/cinder/README.md b/staging/volumes/cinder/README.md index bbb3c470..fec59da2 100644 --- a/staging/volumes/cinder/README.md +++ b/staging/volumes/cinder/README.md @@ -21,7 +21,3 @@ You should now be able to query your web server: $ Hello World ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/cinder/README.md?pixel)]() - diff --git a/staging/volumes/fibre_channel/README.md b/staging/volumes/fibre_channel/README.md index b241d274..e3a203eb 100644 --- a/staging/volumes/fibre_channel/README.md +++ b/staging/volumes/fibre_channel/README.md @@ -86,7 +86,3 @@ $ systemctl enable --now multipathd.service inaccessible block devices as they will be claimed by multipath and exposed as a device in /dev/mapper/*. - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/fibre_channel/README.md?pixel)]() - diff --git a/staging/volumes/flocker/README.md b/staging/volumes/flocker/README.md index 018f7b2c..71276b69 100644 --- a/staging/volumes/flocker/README.md +++ b/staging/volumes/flocker/README.md @@ -110,6 +110,3 @@ Read more about the [Flocker Cluster Architecture](https://docs.clusterhq.com/en To see a demo example of using Kubernetes and Flocker, visit [Flocker's blog post on High Availability with Kubernetes and Flocker](https://clusterhq.com/2015/12/22/ha-demo-kubernetes-flocker/) - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/flocker/README.md?pixel)]() - diff --git a/staging/volumes/nfs/README.md b/staging/volumes/nfs/README.md index 7ce3c594..d270c179 100644 --- a/staging/volumes/nfs/README.md +++ b/staging/volumes/nfs/README.md @@ -170,9 +170,3 @@ Thu Oct 22 19:28:55 UTC 2015 nfs-busybox-w3s4t ``` - - - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/volumes/nfs/README.md?pixel)]() - diff --git a/staging/volumes/nfs/nfs-data/README.md b/staging/volumes/nfs/nfs-data/README.md index df4b26d0..46133f92 100644 --- a/staging/volumes/nfs/nfs-data/README.md +++ b/staging/volumes/nfs/nfs-data/README.md @@ -6,8 +6,3 @@ only NFSv3 is opened in this container. Available as `gcr.io/google-samples/nfs-server` - - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/nfs/nfs-data/README.md?pixel)]() - diff --git a/staging/volumes/portworx/README.md b/staging/volumes/portworx/README.md index f69b3185..eeda3a5f 100644 --- a/staging/volumes/portworx/README.md +++ b/staging/volumes/portworx/README.md @@ -364,7 +364,3 @@ create Portworx volumes out of band and they will be created automatically. pvpod 1/1 Running 0 48m ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/portworx/README.md?pixel)]() - diff --git a/staging/volumes/quobyte/Readme.md b/staging/volumes/quobyte/Readme.md index 4199a232..aa6f3417 100644 --- a/staging/volumes/quobyte/Readme.md +++ b/staging/volumes/quobyte/Readme.md @@ -93,6 +93,3 @@ $ docker inspect --format '{{ range .Mounts }}{{ if eq .Destination "/mnt"}}{{ . /var/lib/kubelet/plugins/kubernetes.io~quobyte/root#root@testVolume ``` - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/quobyte/Readme.md?pixel)]() - diff --git a/staging/volumes/scaleio/README.md b/staging/volumes/scaleio/README.md index 99be02f8..a328010f 100644 --- a/staging/volumes/scaleio/README.md +++ b/staging/volumes/scaleio/README.md @@ -243,6 +243,4 @@ NAME READY STATUS RESTARTS AGE pod-0 1/1 Running 0 23m pod-sio-small 1/1 Running 0 5s ``` - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/scaleio/README.md?pixel)]() - + diff --git a/staging/volumes/vsphere/README.md b/staging/volumes/vsphere/README.md index 0a7a1cc3..b80d61da 100644 --- a/staging/volumes/vsphere/README.md +++ b/staging/volumes/vsphere/README.md @@ -675,6 +675,3 @@ vSphere volumes can be consumed by Stateful Sets. [Download example](simple-statefulset.yaml) - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/vsphere/README.md?pixel)]() - diff --git a/volumes/cephfs/README.md b/volumes/cephfs/README.md index 35140202..0e7af3f7 100644 --- a/volumes/cephfs/README.md +++ b/volumes/cephfs/README.md @@ -38,7 +38,3 @@ Here are the commands: If you ssh to that machine, you can run `docker ps` to see the actual pod and `docker inspect` to see the volumes used by the container. - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/cephfs/README.md?pixel)]() - diff --git a/volumes/glusterfs/README.md b/volumes/glusterfs/README.md index f239914b..25d6d473 100644 --- a/volumes/glusterfs/README.md +++ b/volumes/glusterfs/README.md @@ -114,6 +114,3 @@ $ kubectl exec glusterfs -- mount | grep gluster You may also run `docker ps` on the host to see the actual container. - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/glusterfs/README.md?pixel)]() - diff --git a/volumes/iscsi/README.md b/volumes/iscsi/README.md index b4182d45..03a7f5cf 100644 --- a/volumes/iscsi/README.md +++ b/volumes/iscsi/README.md @@ -130,7 +130,3 @@ Run *docker inspect* and verify the container mounted the host directory into th /var/lib/kubelet/pods/f527ca5b-6d87-11e5-aa7e-080027ff6387/volumes/kubernetes.io~iscsi/iscsipd-rw ``` - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/iscsi/README.md?pixel)]() - diff --git a/volumes/rbd/README.md b/volumes/rbd/README.md index fe7d3558..491d1fc8 100644 --- a/volumes/rbd/README.md +++ b/volumes/rbd/README.md @@ -59,7 +59,3 @@ On the Kubernetes host, I got these in mount output If you ssh to that machine, you can run `docker ps` to see the actual pod and `docker inspect` to see the volumes used by the container. - - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/rbd/README.md?pixel)]() - diff --git a/volumes/storageos/README.md b/volumes/storageos/README.md index ddd9aa10..2ce0e8b5 100644 --- a/volumes/storageos/README.md +++ b/volumes/storageos/README.md @@ -470,6 +470,3 @@ StorageOS supports the following storage class parameters: test-storageos-redis-sc-pvc 1/1 Running 0 44s ``` - -[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/storageos/README.md?pixel)]() -