Typo fix: some word error (#8524)
* Typo fix: Acceptible=>Acceptable and componenets=>components * Typo fix: Availablity=>Availability * Typo fix: implicity=>implicitly
This commit is contained in:
@@ -274,7 +274,7 @@ kubelet
|
|||||||
<td colspan="2">--enforce-node-allocatable stringSlice Default: [pods]</td>
|
<td colspan="2">--enforce-node-allocatable stringSlice Default: [pods]</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td></td><td style="line-height: 130%">A comma separated list of levels of node allocatable enforcement to be enforced by kubelet. Acceptible options are 'pods', 'system-reserved' & 'kube-reserved'. If the latter two options are specified, '--system-reserved-cgroup' & '--kube-reserved-cgroup' must also be set respectively. See https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/ for more details.</td>
|
<td></td><td style="line-height: 130%">A comma separated list of levels of node allocatable enforcement to be enforced by kubelet. Acceptable options are 'pods', 'system-reserved' & 'kube-reserved'. If the latter two options are specified, '--system-reserved-cgroup' & '--kube-reserved-cgroup' must also be set respectively. See https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/ for more details.</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td colspan="2">--event-burst int32 Default: 10</td>
|
<td colspan="2">--event-burst int32 Default: 10</td>
|
||||||
@@ -352,7 +352,7 @@ kubelet
|
|||||||
<td colspan="2">--experimental-check-node-capabilities-before-mount</td>
|
<td colspan="2">--experimental-check-node-capabilities-before-mount</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td></td><td style="line-height: 130%">[Experimental] if set true, the kubelet will check the underlying node for required componenets (binaries, etc.) before performing the mount</td>
|
<td></td><td style="line-height: 130%">[Experimental] if set true, the kubelet will check the underlying node for required components (binaries, etc.) before performing the mount</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<td colspan="2">--experimental-kernel-memcg-notification</td>
|
<td colspan="2">--experimental-kernel-memcg-notification</td>
|
||||||
|
|||||||
@@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
reviewers:
|
reviewers:
|
||||||
- chuckha
|
- chuckha
|
||||||
title: Set up a High-Availablity Etcd Cluster With Kubeadm
|
title: Set up a High-Availability Etcd Cluster With Kubeadm
|
||||||
content_template: templates/task
|
content_template: templates/task
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
@@ -379,7 +379,7 @@ For more information see
|
|||||||
|
|
||||||
It is possible to utilize AWS Route53 as a cloud DNS provider when the
|
It is possible to utilize AWS Route53 as a cloud DNS provider when the
|
||||||
federation controller-manager is run on-premise. The controller-manager
|
federation controller-manager is run on-premise. The controller-manager
|
||||||
Deployment must be configured with AWS credentials since it cannot implicity
|
Deployment must be configured with AWS credentials since it cannot implicitly
|
||||||
gather them from a VM running on AWS.
|
gather them from a VM running on AWS.
|
||||||
|
|
||||||
Currently, `kubefed init` does not read AWS Route53 credentials from the
|
Currently, `kubefed init` does not read AWS Route53 credentials from the
|
||||||
|
|||||||
Reference in New Issue
Block a user