Fix small typos (#18886)
* Fix small typos Small typos noticed and fixed in: - configure-upgrade-etcd.md - reconfigure-kubelet.md Signed-off-by: Mariyan Dimitrov <mariyan.dimitrov@gmail.com> * Rephrase a paragraph on etcd upgrade en\docs\tasks\administer-cluster\configure-upgrade-etcd.md Following a suggestion in #18886, I've rephrased a sentence on etcd upgrade prerequisites. Signed-off-by: Mariyan Dimitrov <mariyan.dimitrov@gmail.com>
This commit is contained in:
@@ -215,8 +215,8 @@ etcd2 and etcd3 is as follows:
|
|||||||
message `etcd2 is no longer a supported storage backend`
|
message `etcd2 is no longer a supported storage backend`
|
||||||
|
|
||||||
Before upgrading a v1.12.x kube-apiserver using `--storage-backend=etcd2` to
|
Before upgrading a v1.12.x kube-apiserver using `--storage-backend=etcd2` to
|
||||||
v1.13.x, etcd v2 data MUST by migrated to the v3 storage backend, and
|
v1.13.x, etcd v2 data must be migrated to the v3 storage backend and
|
||||||
kube-apiserver invocations changed to use `--storage-backend=etcd3`.
|
kube-apiserver invocations must be changed to use `--storage-backend=etcd3`.
|
||||||
|
|
||||||
The process for migrating from etcd2 to etcd3 is highly dependent on how the
|
The process for migrating from etcd2 to etcd3 is highly dependent on how the
|
||||||
etcd cluster was deployed and configured, as well as how the Kubernetes
|
etcd cluster was deployed and configured, as well as how the Kubernetes
|
||||||
|
|||||||
@@ -163,7 +163,7 @@ data:
|
|||||||
```
|
```
|
||||||
|
|
||||||
The ConfigMap is created in the `kube-system` namespace because this
|
The ConfigMap is created in the `kube-system` namespace because this
|
||||||
ConfigMap configures a Kubelet, which is Kubernetes system component.
|
ConfigMap configures a Kubelet, which is a Kubernetes system component.
|
||||||
|
|
||||||
The `--append-hash` option appends a short checksum of the ConfigMap contents
|
The `--append-hash` option appends a short checksum of the ConfigMap contents
|
||||||
to the name. This is convenient for an edit-then-push workflow, because it
|
to the name. This is convenient for an edit-then-push workflow, because it
|
||||||
|
|||||||
Reference in New Issue
Block a user