whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix minor typos and misspells detected using misspell (#7313)

Browse Source
This commit is contained in:
Joseph Herlant
2018-02-08 15:48:52 -08:00
committed by k8s-ci-robot
parent 9a1e5a2c97
commit cef6e06697
8 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/administer-cluster/reconfigure-kubelet.md
+1 -1
View File
@@ -333,7 +333,7 @@ condition's message reverts to either `using current (default)` or
### Deauthorize your Node fom reading the old ConfigMap
Once you know your Node is using the default configuraiton again, it is a good
Once you know your Node is using the default configuration again, it is a good
idea to deauthorize the node from reading the old ConfigMap. Run the following
commands to remove the RoleBinding and Role:
docs/tasks/administer-cluster/running-cloud-controller.md
+1 -1
View File
@@ -25,7 +25,7 @@ Every cloud has their own set of requirements for running their own cloud provid
* cloud authentication/authorization: your cloud may require a token or IAM rules to allow access to their APIs
* kubernetes authentication/authorization: cloud-controller-manager may need RBAC rules set to speak to the kubernetes apiserver
* high availabilty: like kube-controller-manager, you may want a high available setup for cloud controller manager using leader election (on by default).
* high availability: like kube-controller-manager, you may want a high available setup for cloud controller manager using leader election (on by default).
### Running cloud-controller-manager