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

Propose small spelling changes (#184)

This commit is contained in:
John Eismeier 2018-01-31 12:17:25 -05:00 committed by Ahmet Alp Balkan
parent cee89cecb7
commit 826d825c0b
4 changed files with 20 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
staging/https-nginx/index2.html
View File

@ -12,7 +12,7 @@
</head> </head>
<body> <body>
<h1>Nginx has been reloaded!</h1> <h1>Nginx has been reloaded!</h1>
<p>If you see this page, the nginx web server has been automaticly reloaded, since the config file has been updated using <a href="https://github.com/kubernetes/kubernetes">Kubernetes</a>.</p> <p>If you see this page, the nginx web server has been automatically reloaded, since the config file has been updated using <a href="https://github.com/kubernetes/kubernetes">Kubernetes</a>.</p>
<p>For online documentation and support please refer to <p>For online documentation and support please refer to

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

@ -147,11 +147,11 @@ For example:
For available volume types and its administration options refer: ([Administration Guide](http://docs.gluster.org/en/latest/Administrator%20Guide/Setting%20Up%20Volumes/)) For available volume types and its administration options refer: ([Administration Guide](http://docs.gluster.org/en/latest/Administrator%20Guide/Setting%20Up%20Volumes/))
* `volumeoptions` : This option allows to specify the gluster volume option which has to be set on the dynamically provisioned GlusterFS volume. The value string should be comma seperated strings which need to be set on the volume. As shown in example, if you want to enable encryption on gluster dynamically provisioned volumes you can pass `client.ssl on, server.ssl on` options. This is an optional parameter. * `volumeoptions` : This option allows to specify the gluster volume option which has to be set on the dynamically provisioned GlusterFS volume. The value string should be comma separated strings which need to be set on the volume. As shown in example, if you want to enable encryption on gluster dynamically provisioned volumes you can pass `client.ssl on, server.ssl on` options. This is an optional parameter.
For available volume options and its administration refer: ([Administration Guide](http://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/)) For available volume options and its administration refer: ([Administration Guide](http://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/))
* `volumenameprefix` : By default dynamically provisioned volumes has the naming schema of `vol_UUID` format. With this option present in storageclass, an admin can now prefix the desired volume name from storageclass. If `volumenameprefix` storageclass parameter is set, the dynamically provisioned volumes are created in below format where `_` is the field seperator/delimiter: * `volumenameprefix` : By default dynamically provisioned volumes has the naming schema of `vol_UUID` format. With this option present in storageclass, an admin can now prefix the desired volume name from storageclass. If `volumenameprefix` storageclass parameter is set, the dynamically provisioned volumes are created in below format where `_` is the field separator/delimiter:
`volumenameprefix_Namespace_PVCname_randomUUID` `volumenameprefix_Namespace_PVCname_randomUUID`
@ -280,19 +280,19 @@ Access Modes: RWO
No events. No events.
$ kubectl describe pv $ kubectl describe pv
Name: pvc-bdb82652-694a-11e6-b811-080027242396 Name: pvc-bdb82652-694a-11e6-b811-080027242396
Labels: <none> Labels: <none>
Status: Bound Status: Bound
Claim: default/claim1 Claim: default/claim1
Reclaim Policy: Delete Reclaim Policy: Delete
Access Modes: RWO Access Modes: RWO
Capacity: 3Gi Capacity: 3Gi
Message: Message:
Source: Source:
Type: Quobyte (a Quobyte mount on the host that shares a pod's lifetime) Type: Quobyte (a Quobyte mount on the host that shares a pod's lifetime)
Registry: 138.68.79.14:7861 Registry: 138.68.79.14:7861
Volume: kubernetes-dynamic-pvc-bdb97c58-694a-11e6-91b6-080027242396 Volume: kubernetes-dynamic-pvc-bdb97c58-694a-11e6-91b6-080027242396
ReadOnly: false ReadOnly: false
No events. No events.
``` ```
@ -440,7 +440,7 @@ The kube-controller-manager is now able to provision storage, however we still n
$ ceph osd pool create kube 512 $ ceph osd pool create kube 512
$ ceph auth get-or-create client.kube mon 'allow r' osd 'allow rwx pool=kube' $ ceph auth get-or-create client.kube mon 'allow r' osd 'allow rwx pool=kube'
[client.kube] [client.kube]
key = AQBQyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy== key = AQBQyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy==
``` ```
This key will be made into a secret, just like the admin secret. However this user secret will need to be created in every namespace where you intend to consume RBD volumes provisioned in our example storage class. Let's create a namespace called `myns`, and create the user secret in that namespace. This key will be made into a secret, just like the admin secret. However this user secret will need to be created in every namespace where you intend to consume RBD volumes provisioned in our example storage class. Let's create a namespace called `myns`, and create the user secret in that namespace.
@ -486,7 +486,7 @@ Source:
Type: RBD (a Rados Block Device mount on the host that shares a pod's lifetime) Type: RBD (a Rados Block Device mount on the host that shares a pod's lifetime)
CephMonitors: [127.0.0.1:6789] CephMonitors: [127.0.0.1:6789]
RBDImage: kubernetes-dynamic-pvc-1cfb1862-664b-11e6-9a5d-90b11c09520d RBDImage: kubernetes-dynamic-pvc-1cfb1862-664b-11e6-9a5d-90b11c09520d
FSType: FSType:
RBDPool: kube RBDPool: kube
RadosUser: kube RadosUser: kube
Keyring: /etc/ceph/keyring Keyring: /etc/ceph/keyring

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

@ -60,7 +60,7 @@ spec:
<!-- END MUNGE: EXAMPLE ./quobyte-pod.yaml --> <!-- END MUNGE: EXAMPLE ./quobyte-pod.yaml -->
Parameters: Parameters:
* **registry** Quobyte registry to use to mount the volume. You can specifiy the registry as <host>:<port> pair or if you want to specify multiple registries you just have to put a comma between them e.q. <host1>:<port>,<host2>:<port>,<host3>:<port>. The host can be an IP address or if you have a working DNS you can also provide the DNS names. * **registry** Quobyte registry to use to mount the volume. You can specify the registry as <host>:<port> pair or if you want to specify multiple registries you just have to put a comma between them e.q. <host1>:<port>,<host2>:<port>,<host3>:<port>. The host can be an IP address or if you have a working DNS you can also provide the DNS names.
* **volume** volume represents a Quobyte volume which must be created before usage. * **volume** volume represents a Quobyte volume which must be created before usage.
* **readOnly** is the boolean that sets the mountpoint readOnly or readWrite. * **readOnly** is the boolean that sets the mountpoint readOnly or readWrite.
* **user** maps all access to this user. Default is `root`. * **user** maps all access to this user. Default is `root`.

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

@ -96,10 +96,10 @@
volumePath: "[datastore1] volumes/myDisk" volumePath: "[datastore1] volumes/myDisk"
fsType: ext4 fsType: ext4
``` ```
In the above example datastore1 is located in the root folder. If datastore is member of Datastore Cluster or located in sub folder, the folder path needs to be provided in the VolumePath as below. In the above example datastore1 is located in the root folder. If datastore is member of Datastore Cluster or located in sub folder, the folder path needs to be provided in the VolumePath as below.
```yaml ```yaml
vsphereVolume: vsphereVolume:
VolumePath: "[DatastoreCluster/datastore1] volumes/myDisk" VolumePath: "[DatastoreCluster/datastore1] volumes/myDisk"
``` ```
[Download example](vsphere-volume-pv.yaml?raw=true) [Download example](vsphere-volume-pv.yaml?raw=true)
@ -240,7 +240,7 @@
parameters: parameters:
diskformat: zeroedthick diskformat: zeroedthick
datastore: VSANDatastore datastore: VSANDatastore
``` ```
If datastore is member of DataStore Cluster or within some sub folder, the datastore folder path needs to be provided in the datastore parameter as below. If datastore is member of DataStore Cluster or within some sub folder, the datastore folder path needs to be provided in the datastore parameter as below.
```yaml ```yaml
@ -258,7 +258,7 @@
Verifying storage class is created: Verifying storage class is created:
``` bash ``` bash
$ kubectl describe storageclass fast $ kubectl describe storageclass fast
Name: fast Name: fast
IsDefaultClass: No IsDefaultClass: No
Annotations: <none> Annotations: <none>
@ -382,7 +382,7 @@
__Note: Here you don't need to create persistent volume it is created for you.__ __Note: Here you don't need to create persistent volume it is created for you.__
1. Create Storage Class. 1. Create Storage Class.
Example 1: Example 1:
```yaml ```yaml
@ -420,7 +420,7 @@
Vsphere Infrastructure(VI) Admins will have the ability to specify custom Virtual SAN Storage Capabilities during dynamic volume provisioning. You can now define storage requirements, such as performance and availability, in the form of storage capabilities during dynamic volume provisioning. The storage capability requirements are converted into a Virtual SAN policy which are then pushed down to the Virtual SAN layer when a persistent volume (virtual disk) is being created. The virtual disk is distributed across the Virtual SAN datastore to meet the requirements. Vsphere Infrastructure(VI) Admins will have the ability to specify custom Virtual SAN Storage Capabilities during dynamic volume provisioning. You can now define storage requirements, such as performance and availability, in the form of storage capabilities during dynamic volume provisioning. The storage capability requirements are converted into a Virtual SAN policy which are then pushed down to the Virtual SAN layer when a persistent volume (virtual disk) is being created. The virtual disk is distributed across the Virtual SAN datastore to meet the requirements.
The official [VSAN policy documentation](https://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.vsphere.virtualsan.doc%2FGUID-08911FD3-2462-4C1C-AE81-0D4DBC8F7990.html) describes in detail about each of the individual storage capabilities that are supported by VSAN. The user can specify these storage capabilities as part of storage class defintion based on his application needs. The official [VSAN policy documentation](https://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.vsphere.virtualsan.doc%2FGUID-08911FD3-2462-4C1C-AE81-0D4DBC8F7990.html) describes in detail about each of the individual storage capabilities that are supported by VSAN. The user can specify these storage capabilities as part of storage class definition based on his application needs.
The policy settings can be one or more of the following: The policy settings can be one or more of the following: