The default kubelet configuration ConfigMap that kubeadm manages
is "kubelet-config" instead of "kubelet-config-x.yy" (where x.yy
is the Kubernetes version) in 1.24.
Cleanup references to the legacy naming in kubeadm documentation.
Generated contents in content/en/docs/reference/* are not updated.
The command "kubeadm kubeconfig user" is missing
some examples and more details on why it is needed.
- Add a new section "Generating kubeconfig files
for additional users" under the kubeadm-certs page.
- Link to this section from the kubeadm-kubeconfig reference page.
- Link to this section from the create-cluster-kubeadm page.
Touch the following files:
- Implementation details: remove docker specifics, which is changing
in 1.24
- Create cluster: small language cleanup, remove note about 1.24
- Install kubeadm: Include two up-to-date tables for Linux / Windows
with known endpoints. Include cri-dockerd.
- Kubelet integration: (side cleanup) use "container runtime" instead of
"CRI runtime" (which is incorrect). Mention that only updating
"--container-runtime-endpoint=.." is required if the user wishes
to override the CR on a certain host. Dockershim->CR-foo migration
guides would make the "--container-runtime=remote" flag explicit
and we want to remove it at some point.
- Troubleshooting kubeadm: Remove some instances of Docker troubleshooting
that imply docker as default CR, or talk about old Docker versions.
Be more generic about container runtimes.
- Adding Windows nodes: move the containerd tab before the Docker
tab, as containerd is now the default. Remove note about being explicit
about --cri-socket. Add note that crictl is required for both
Docker and containerd. Add note that cri-dockerd is required if
the user wants to use Docker EE on Windows.
The current entry under additional information about drain can
be confusing and users might jump into draining the nodes before
the upgrade steps (as a pre-req), following the
instructions in the external link. This is not accurate.
Adjust the entry text to explain that drain is a step as part of
the upgrade process and this additional information entry just
mentions why it is needed.
* Update kubeadm-upgrade.md
`apt-mark hold` is still required when `apt-get` is used with `--allow-change-held-packages`.
`--allow-change-held-packages` unholds the package but it doesn't pin the new version.
* Add missing changes
* Update kubeadm-upgrade.md
Remove apt >1.1 examples.
In 1.22 kubeadm is adding a new API version - v1beta3.
Adapt links and examples to use v1beta3 instead of v1beta2.
v1beta2 is not deprecated yet, but v1beta3 is preferred
at this point.
break long lines
simplify wording (suggested by neolit123)
phrasing error/typo
don't mention creating a new kuebadm config file, not really relevant here
remove unnecessary stop from kubelet cert troubleshoot
minor phrasing improvement: *the* kublet
make the steps for fixing kubelet certs separate from other troubleshooting suggestions
move kubelet cert troubleshooting to a better place
improve note wording and add link
add missing dot
Co-authored-by: Lubomir I. Ivanov <neolit123@gmail.com>
add missing dot
Co-authored-by: Lubomir I. Ivanov <neolit123@gmail.com>
remove steps not related to the issue
Make instructions work on worker nodes too
Co-authored-by: Lubomir I. Ivanov <neolit123@gmail.com>
Include a new section of the kubeadm certificate management page
to talk about kubelet serving certificates and how to make
them signed. Also include a note about using secure connection
with the metrics-server.
Kubernetes Prow Robot
Lubomir I. Ivanov
Nate W
Clément Nussbaumer
Erico Fusco
sandipanpanda
Ashley Davis
Jacob Valdemar
silenceshell
Jacob Valdemar
Yuiko Mouri
Victor Palade
Shubham Kuchhal
Steven Yan
aliakbar
Qiming Teng
Luke Ingalls
Ritu Panjwani
Antoine Poliakov
Jihoon Seo
Paco Xu
Priyanka Saggu
Shannon Kularathna
Tim Bannister