Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix small typos #18886

Merged
merged 2 commits into from
Jan 29, 2020
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,7 @@ etcd2 and etcd3 is as follows:
message `etcd2 is no longer a supported storage backend`

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`.
merkata marked this conversation as resolved.
Show resolved Hide resolved

The process for migrating from etcd2 to etcd3 is highly dependent on how the
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ data:
```

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
to the name. This is convenient for an edit-then-push workflow, because it
Expand Down