kubernetes
/
examples
mirror of https://github.com/kubernetes/examples.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clean up broken analytics links

This commit is contained in:
Janet Kuo 2025-05-19 10:09:55 -07:00
parent 1b9f904307
commit e6f04c498b
54 changed files with 1 additions and 205 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
cassandra/java/README.md
View File

@ -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. This in affect makes every node a seed provider, which is not a recommended best practice. This increases maintenance and reduces gossip performance.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storage/cassandra/java/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
guestbook-go/README.md
View File

@ -265,7 +265,3 @@ redis-replica
Tip: To turn down your Kubernetes cluster, follow the corresponding instructions in the version of the 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. [Getting Started Guides](https://kubernetes.io/docs/getting-started-guides/) that you previously used to create your cluster.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/guestbook-go/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

5
guidelines.md
View File

@ -137,8 +137,3 @@ Each example must be well-structured and documented to ensure clarity and usabil
potential incompatibility with current Kubernetes versions. potential incompatibility with current Kubernetes versions.
* Community Maintenance: SIG Apps will act as the overall steward, and individual example * 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. maintainers (original authors or new volunteers) are crucial for the health of the repository.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/guidelines.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
mysql-cinder-pd/README.md
View File

@ -45,7 +45,3 @@ This should now
3. Mount it on the kubelet's host machine 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 4. Spin up a container with this volume mounted to the path specified in the pod definition
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/mysql-cinder-pd/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/cluster-dns/README.md
View File

@ -180,7 +180,3 @@ kubectl create -f examples/staging/cluster-dns/dns-frontend-pod.yaml
kubectl logs dns-frontend kubectl logs dns-frontend
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/cluster-dns/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/cockroachdb/README.md
View File

@ -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 kubectl delete statefulsets,persistentvolumes,persistentvolumeclaims,services,poddisruptionbudget -l app=cockroachdb
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/cockroachdb/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/elasticsearch/README.md
View File

@ -189,6 +189,3 @@ You should see something similar to the following:
} }
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/elasticsearch/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/elasticsearch/production_cluster/README.md
View File

@ -190,7 +190,3 @@ You should see something similar to the following:
} }
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/elasticsearch/production_cluster/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/explorer/README.md
View File

@ -127,7 +127,3 @@ Error: &lt;*&gt;lookup elasticsearch-logging: no such host
</body></html> </body></html>
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/explorer/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/https-nginx/README.md
View File

@ -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/). 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/).
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/https-nginx/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/javaee/README.md
View File

@ -128,7 +128,3 @@ kubectl delete -f examples/javaee/mysql-service.yaml
kubectl delete -f examples/javaee/wildfly-rc.yaml kubectl delete -f examples/javaee/wildfly-rc.yaml
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/javaee/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

5
staging/javaweb-tomcat-sidecar/README.md
View File

@ -177,8 +177,3 @@ All resources created in this application can be deleted:
$ kubectl delete -f examples/javaweb-tomcat-sidecar/javaweb-2.yaml $ kubectl delete -f examples/javaweb-tomcat-sidecar/javaweb-2.yaml
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/javaweb-tomcat-sidecar/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/job/expansions/README.md
View File

@ -1,7 +1,3 @@
This file has moved to: http://kubernetes.io/docs/user-guide/jobs/ This file has moved to: http://kubernetes.io/docs/user-guide/jobs/
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/job/expansions/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/job/work-queue-1/README.md
View File

@ -1,7 +1,3 @@
This file has moved to: http://kubernetes.io/docs/user-guide/jobs/ This file has moved to: http://kubernetes.io/docs/user-guide/jobs/
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/job/work-queue-1/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/job/work-queue-2/README.md
View File

@ -1,7 +1,3 @@
This file has moved to: http://kubernetes.io/docs/user-guide/jobs/ This file has moved to: http://kubernetes.io/docs/user-guide/jobs/
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/job/work-queue-2/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/meteor/README.md
View File

@ -209,7 +209,3 @@ container section:
], ],
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/meteor/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/meteor/dockerbase/README.md
View File

@ -8,7 +8,3 @@ To build and push the base meteor-kubernetes image:
docker build -t chees/meteor-kubernetes . docker build -t chees/meteor-kubernetes .
docker push chees/meteor-kubernetes docker push chees/meteor-kubernetes
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/meteor/dockerbase/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/newrelic-infrastructure/README.md
View File

@ -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.) 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.)
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/newrelic/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/newrelic/README.md
View File

@ -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. 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.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/newrelic/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/nodesjs-mongodb/README.md
View File

@ -277,6 +277,3 @@ With Google Cloud Platform, get the IP address of all load balancers with the fo
gcloud compute forwarding-rules list gcloud compute forwarding-rules list
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/nodesjs-mongodb/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/openshift-origin/README.md
View File

@ -205,7 +205,3 @@ Clean up your cluster from resources created with this example:
$ ${OPENSHIFT_EXAMPLE}/cleanup.sh $ ${OPENSHIFT_EXAMPLE}/cleanup.sh
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/openshift-origin/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/persistent-volume-provisioning/README.md
View File

@ -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 /dev/rbd1 2.9G 4.5M 2.8G 1% /var/lib/www/html
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/persistent-volume-provisioning/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/phabricator/README.md
View File

@ -210,7 +210,3 @@ To turn down a Kubernetes cluster:
$ cluster/kube-down.sh $ cluster/kube-down.sh
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/phabricator/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/podsecuritypolicy/rbac/README.md
View File

@ -243,6 +243,3 @@ $ kubectl get pod nginx -o yaml | egrep "psp|privileged"
privileged: true privileged: true
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/podsecuritypolicy/rbac/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/runtime-constraints/README.md
View File

@ -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 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. 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.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/runtime-constraints/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/selenium/README.md
View File

@ -188,7 +188,3 @@ kubectl delete deployment selenium-python
kubectl delete svc selenium-hub kubectl delete svc selenium-hub
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/selenium/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/sharing-clusters/README.md
View File

@ -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) For a more advanced example of sharing clusters, see the [service-loadbalancer](https://github.com/kubernetes/contrib/tree/master/service-loadbalancer/README.md)
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/sharing-clusters/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/simple-nginx.md
View File

@ -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) 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. is given in a different document.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/simple-nginx.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/spark/README.md
View File

@ -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 top right as well), the `port-forward` probably failed and needs to be
restarted. See #12179. restarted. See #12179.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/spark/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/spark/spark-gluster/README.md
View File

@ -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 root@spark-master-controller-c1sqd:/# ls -l /mnt/glusterfs/output
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/spark/spark-gluster/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/storage/hazelcast/README.md
View File

@ -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) See [here](https://github.com/pires/hazelcast-kubernetes-bootstrapper/blob/master/src/main/java/com/github/pires/hazelcast/HazelcastDiscoveryController.java)
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storage/hazelcast/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

5
staging/storage/mysql-galera/README.md
View File

@ -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. 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.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storage/mysql-galera/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/storage/redis/README.md
View File

@ -128,7 +128,3 @@ kubectl scale rc redis-sentinel --replicas=3
kubectl delete pods redis-master kubectl delete pods redis-master
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/storage/redis/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/storage/rethinkdb/README.md
View File

@ -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 * see [antmanler/rethinkdb-k8s](https://github.com/antmanler/rethinkdb-k8s) for detail
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storage/rethinkdb/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/storage/vitess/README.md
View File

@ -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. You may also want to remove any firewall rules you created.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storage/vitess/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/storm/README.md
View File

@ -166,7 +166,3 @@ Make sure the Nimbus Pod is running.
```kubectl create -f storm-worker-controller.yaml``` ```kubectl create -f storm-worker-controller.yaml```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/storm/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

5
staging/sysdig-cloud/README.md
View File

@ -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: Please see the Sysdig Cloud support site for the latest documentation:
http://support.sysdigcloud.com/hc/en-us/sections/200959909 http://support.sysdigcloud.com/hc/en-us/sections/200959909
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/sysdig-cloud/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/volumes/aws_ebs/README.md
View File

@ -31,7 +31,3 @@ You should now be able to query your web server:
$ Hello World $ Hello World
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/aws_ebs/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/volumes/azure_disk/README.md
View File

@ -18,6 +18,3 @@ Launch the Pod:
# kubectl create -f examples/staging/volumes/azure_disk/azure.yaml # kubectl create -f examples/staging/volumes/azure_disk/azure.yaml
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/volumes/azure_disk/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/volumes/azure_file/README.md
View File

@ -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). 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).
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/azure_file/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/volumes/cinder/README.md
View File

@ -21,7 +21,3 @@ You should now be able to query your web server:
$ Hello World $ Hello World
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/cinder/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/volumes/fibre_channel/README.md
View File

@ -86,7 +86,3 @@ $ systemctl enable --now multipathd.service
inaccessible block devices as they will be claimed by multipath and inaccessible block devices as they will be claimed by multipath and
exposed as a device in /dev/mapper/*. exposed as a device in /dev/mapper/*.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/fibre_channel/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/volumes/flocker/README.md
View File

@ -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/) 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/)
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/flocker/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

6
staging/volumes/nfs/README.md
View File

@ -170,9 +170,3 @@ Thu Oct 22 19:28:55 UTC 2015
nfs-busybox-w3s4t nfs-busybox-w3s4t
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/staging/volumes/nfs/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

5
staging/volumes/nfs/nfs-data/README.md
View File

@ -6,8 +6,3 @@ only NFSv3 is opened in this container.
Available as `gcr.io/google-samples/nfs-server` Available as `gcr.io/google-samples/nfs-server`
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/nfs/nfs-data/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/volumes/portworx/README.md
View File

@ -364,7 +364,3 @@ create Portworx volumes out of band and they will be created automatically.
pvpod 1/1 Running 0 48m pvpod 1/1 Running 0 48m
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/portworx/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/volumes/quobyte/Readme.md
View File

@ -93,6 +93,3 @@ $ docker inspect --format '{{ range .Mounts }}{{ if eq .Destination "/mnt"}}{{ .
/var/lib/kubelet/plugins/kubernetes.io~quobyte/root#root@testVolume /var/lib/kubelet/plugins/kubernetes.io~quobyte/root#root@testVolume
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/quobyte/Readme.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
staging/volumes/scaleio/README.md
View File

@ -243,6 +243,4 @@ NAME READY STATUS RESTARTS AGE
pod-0 1/1 Running 0 23m pod-0 1/1 Running 0 23m
pod-sio-small 1/1 Running 0 5s pod-sio-small 1/1 Running 0 5s
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/scaleio/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
staging/volumes/vsphere/README.md
View File

@ -675,6 +675,3 @@ vSphere volumes can be consumed by Stateful Sets.
[Download example](simple-statefulset.yaml) [Download example](simple-statefulset.yaml)
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/vsphere/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
volumes/cephfs/README.md
View File

@ -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. 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.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/cephfs/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
volumes/glusterfs/README.md
View File

@ -114,6 +114,3 @@ $ kubectl exec glusterfs -- mount | grep gluster
You may also run `docker ps` on the host to see the actual container. You may also run `docker ps` on the host to see the actual container.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/glusterfs/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
volumes/iscsi/README.md
View File

@ -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 /var/lib/kubelet/pods/f527ca5b-6d87-11e5-aa7e-080027ff6387/volumes/kubernetes.io~iscsi/iscsipd-rw
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/iscsi/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

4
volumes/rbd/README.md
View File

@ -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. 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.
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/rbd/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->

3
volumes/storageos/README.md
View File

@ -470,6 +470,3 @@ StorageOS supports the following storage class parameters:
test-storageos-redis-sc-pvc 1/1 Running 0 44s test-storageos-redis-sc-pvc 1/1 Running 0 44s
``` ```
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/examples/volumes/storageos/README.md?pixel)]()
<!-- END MUNGE: GENERATED_ANALYTICS -->