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

Fix typo fom -> from (#8758)

Browse Source
This commit is contained in:
Justin Santa Barbara
2018-05-29 23:37:55 -07:00
committed by k8s-ci-robot
parent f46e8c3a52
commit 4453e3a483
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/administer-cluster/reconfigure-kubelet.md
+2 -2
View File
@@ -295,7 +295,7 @@ look for the `KubeletConfigOK` condition in `status.conditions`. You should see
`using current: /api/v1/namespaces/kube-system/configmaps/${NEW_CONFIG_MAP_NAME}` when the Kubelet starts using the
new configuration.
### Deauthorize your Node fom reading the old ConfigMap
### Deauthorize your Node from reading the old ConfigMap
Once you know your Node is using the new configuration and are confident that
the new configuration has not caused any problems, it is a good idea to
@@ -331,7 +331,7 @@ remove the `spec.configSource` subfield.
After removing this subfield, you should eventually observe that the KubeletConfigOK
condition's message reverts to `using current: local`.
### Deauthorize your Node fom reading the old ConfigMap
### Deauthorize your Node from reading the old ConfigMap
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