-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Update kubeadm CRI detection docs in light of dockershim deprecation #32761
Update kubeadm CRI detection docs in light of dockershim deprecation #32761
Conversation
/sig cluster-lifecycle |
✅ Deploy Preview for kubernetes-io-main-staging ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
/assign @SergeyKanzhelev |
{{< /table >}} | ||
|
||
<br /> | ||
If both Docker and containerd are detected, Docker takes precedence. This is | ||
If both Docker Engine and containerd are detected, the kubelet gives precedence to Docker Engine. This is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SergeyKanzhelev , is this still true in v1.24?
Seeing if we need to make a follow-up PR to the dev-1.24
branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the 1.24 PR merged here, the behavior is different in 1.24:
https://github.com/kubernetes/website/pull/31309/files#diff-548585d5ff3dc7ff8a61b658052d84f223adca9361c9a4df3a8ce1105d9413bbR94-R95
If both Docker Engine and containerd are detected, the kubelet gives precedence to Docker Engine. This is
kubelet has no precedence or detection. it just defaults flag / config to docker in <1.24.
the "Docker Engine" rename seems fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wouldn't this PR conflict with #31309 when k/website branches are merged?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Part of the release docs process is to merge main into the release docs branch. For these changes, I'd expect that that merge should make sure that the v1.24 changes win (and I hope that's obvious enough). This comment should serve as an extra hint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy if none of the changes from this PR survive into v1.24 docs.
LGTM from docs perspective |
content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md
Outdated
Show resolved
Hide resolved
9de70a1
to
bbe8e54
Compare
content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md
Outdated
Show resolved
Hide resolved
Update kubeadm CRI detection docs in light of dockershim deprecation. Co-authored-by: Lubomir I. Ivanov <[email protected]>
b247c1a
to
9c8227a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: b73b167b6b2c8f5d314a2bd3ed2b8832c73954c9
|
/assign @reylejano |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: reylejano The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes issue #26780
Preview: https://deploy-preview-32761--kubernetes-io-main-staging.netlify.app/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#installing-runtime
This change is for v1.23; I expect that v1.24 changes will overwrite this.
/sig cluster-lifecycle node
/language en
/priority important-longterm