-
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
Add info about finding the runtime endpoint #32132
Add info about finding the runtime endpoint #32132
Conversation
✅ Deploy Preview for kubernetes-io-main-staging ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
Thanks @shannonxtreme
Here's some tweaks I thought of. I hope these help.
content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md
Outdated
Show resolved
Hide resolved
317ed75
to
2dbed30
Compare
@sftim I changed the commands to look for the kubelet process cmdline and analyse the |
@kubernetes/sig-node-pr-reviews does this look technically correct? |
content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md
Outdated
Show resolved
Hide resolved
2dbed30
to
9244b10
Compare
@kubernetes/sig-node-pr-reviews this would be great to get an LGTM on asap :) |
Should we mention the kubectl-detector-for-docker-socket tool here? https://github.com/aws-containers/kubectl-detector-for-docker-socket |
It's third party software. On the other hand it's tool to accomplish this specific task. I'd suggest that we mention the tool, but link to it rather than document how to use it (which is what https://kubernetes.io/docs/contribute/style/content-guide/#what-s-allowed cares about). |
@kubernetes/sig-node-pr-reviews does this change look OK from a technical perspective? Any concerns? |
this looks fine for sig-node. /lgtm |
LGTM label has been added. Git tree hash: 548a065d5b0113c3841a4cf9fb8ce9f20193e459
|
/lgtm |
In some cases, you might find it useful to know which socket your nodes use. For | ||
example, with the removal of dockershim in Kubernetes 1.24 and later, Docker | ||
Engine cannot communicate with the kubelet if it listens on the | ||
`unix:///var/run/dockershim.sock` endpoint. |
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 don't understand this sentence. What communication Between Docker and kubelet is meant here? It is typically kubelet calls into the docker and it uses docker.sock
to call to it. dokershim.sock is only exposed by kubelet to emulate the CRI from dockershim
content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md
Outdated
Show resolved
Hide resolved
process manually. | ||
|
||
1. In the output, look for the `--container-runtime` flag and the | ||
`--container-runtime-endpoint` flag. |
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 think just looking at container-runtime should be enough. If not remote than it's dockershim
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 made a couple of tweaks.
content/en/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use.md
Outdated
Show resolved
Hide resolved
9244b10
to
d3ad42f
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.
Changes since most recent LGTM are trivial (or trivial enough).
/lgtm
/approve
Thanks @shannonxtreme
LGTM label has been added. Git tree hash: bf15a856378ecc3a7ed9c1f94e6b3aa4d572be1e
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim 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 #30974
Add a section to "Find out what container runtime is used on a node" to find the runtime endpoint, with a clarification that Docker users who use cri-dockerd already wouldn't be affected by the dockershim removal.
/sig docs
/language en
/cc @sftim @afbjorklund