github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-10 21:50:05 +00:00
Code Issues Projects Releases Wiki Activity

Updating docs/ to v1

Browse Source
This commit is contained in:
Kris Rousey
2015-06-05 12:47:15 -07:00
parent 640c40da65
commit 6e83eb2636
41 changed files with 116 additions and 117 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/volumes.md
View File

@@ -3,7 +3,7 @@ This document describes the current state of Volumes in kubernetes. Familiarity
A Volume is a directory, possibly with some data in it, which is accessible to a Container. Kubernetes Volumes are similar to but not the same as [Docker Volumes](https://docs.docker.com/userguide/dockervolumes/).
A Pod specifies which Volumes its containers need in its [spec.volumes](http://kubernetes.io/third_party/swagger-ui/#!/v1beta3/createPod) property.
A Pod specifies which Volumes its containers need in its [spec.volumes](http://kubernetes.io/third_party/swagger-ui/#!/v1/createPod) property.
A process in a Container sees a filesystem view composed from two sources: a single Docker image and zero or more Volumes. A [Docker image](https://docs.docker.com/userguide/dockerimages/) is at the root of the file hierarchy. Any Volumes are mounted at points on the Docker image; Volumes do not mount on other Volumes and do not have hard links to other Volumes. Each container in the Pod independently specifies where on its image to mount each Volume. This is specified in each container's VolumeMounts property.
@@ -61,7 +61,7 @@ gcloud compute disks create --size=500GB --zone=us-central1-a my-data-disk
#### GCE PD Example configuration:
```yaml
apiVersion: v1beta3
apiVersion: v1
kind: Pod
metadata:
name: testpd