'etc' should be 'etc.'

Signed-off-by: YuPengZTE <yu.peng36@zte.com.cn>
This commit is contained in:
YuPengZTE
2016-09-22 16:22:31 +08:00
parent f2465eec29
commit f2b90fa2c3
4 changed files with 4 additions and 4 deletions
+1 -1
View File
@@ -62,7 +62,7 @@ There is a specific `cluster/rackspace` directory with the scripts for the follo
## Network Design ## Network Design
- eth0 - Public Interface used for servers/containers to reach the internet - eth0 - Public Interface used for servers/containers to reach the internet
- eth1 - ServiceNet - Intra-cluster communication (k8s, etcd, etc) communicate via this interface. The `cloud-config` files use the special CoreOS identifier `$private_ipv4` to configure the services. - eth1 - ServiceNet - Intra-cluster communication (k8s, etcd, etc.) communicate via this interface. The `cloud-config` files use the special CoreOS identifier `$private_ipv4` to configure the services.
- eth2 - Cloud Network - Used for k8s pods to communicate with one another. The proxy service will pass traffic via this interface. - eth2 - Cloud Network - Used for k8s pods to communicate with one another. The proxy service will pass traffic via this interface.
## Support Level ## Support Level
+1 -1
View File
@@ -72,7 +72,7 @@ accomplished in two ways:
pod network through traffic encapsulation (e.g vxlan). pod network through traffic encapsulation (e.g vxlan).
- Encapsulation reduces performance, though exactly how much depends on your solution. - Encapsulation reduces performance, though exactly how much depends on your solution.
- **Without an overlay network** - **Without an overlay network**
- Configure the underlying network fabric (switches, routers, etc) to be aware of pod IP addresses. - Configure the underlying network fabric (switches, routers, etc.) to be aware of pod IP addresses.
- This does not require the encapsulation provided by an overlay, and so can achieve - This does not require the encapsulation provided by an overlay, and so can achieve
better performance. better performance.
+1 -1
View File
@@ -157,7 +157,7 @@ parallelism, for a variety or reasons:
remaining completions. Higher values of `.spec.parallelism` are effectively ignored. remaining completions. Higher values of `.spec.parallelism` are effectively ignored.
- For work queue jobs, no new pods are started after any pod has succeeded -- remaining pods are allowed to complete, however. - For work queue jobs, no new pods are started after any pod has succeeded -- remaining pods are allowed to complete, however.
- If the controller has not had time to react. - If the controller has not had time to react.
- If the controller failed to create pods for any reason (lack of ResourceQuota, lack of permission, etc), - If the controller failed to create pods for any reason (lack of ResourceQuota, lack of permission, etc.),
then there may be fewer pods than requested. then there may be fewer pods than requested.
- The controller may throttle new pod creation due to excessive previous pod failures in the same Job. - The controller may throttle new pod creation due to excessive previous pod failures in the same Job.
- When a pod is gracefully shutdown, it make take time to stop. - When a pod is gracefully shutdown, it make take time to stop.
+1 -1
View File
@@ -485,7 +485,7 @@ spec:
## Resources ## Resources
The storage media (Disk, SSD, etc) of an `emptyDir` volume is determined by the The storage media (Disk, SSD, etc.) of an `emptyDir` volume is determined by the
medium of the filesystem holding the kubelet root dir (typically medium of the filesystem holding the kubelet root dir (typically
`/var/lib/kubelet`). There is no limit on how much space an `emptyDir` or `/var/lib/kubelet`). There is no limit on how much space an `emptyDir` or
`hostPath` volume can consume, and no isolation between containers or between `hostPath` volume can consume, and no isolation between containers or between