-
Notifications
You must be signed in to change notification settings - Fork 701
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
FEATURE REQUEST: Add kubelet instance configuration to configure CRI socket for each node #3042
Comments
/cc @neolit123 @pacoxu |
@HirazawaUi we need a KEP for this, ket's see what @pacoxu can comment about the previous work done on this. @pacoxu can you please post links to your previous KEP work.? maybe we can close KEP PRs and let @HirazawaUi to take over. |
also are you willing to work on this @HirazawaUi
too many questions |
Yes, I'll try to finish it. |
@pacoxu What do you think about this? I would love to hear your comments :) |
The KEP
My current proposal would be something like kubernetes/enhancements#3930 (comment)
|
Thanks, I have missed this comment, I will resurrect kep as soon as possible. |
Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST
Anything else we need to know?
This issue wants to remove container runtime interface (CRI) socket annotations from Node objects in Kubernetes and no longer added
--container-runtime-endpoint
args inkubeadm-flags.env
(--container-runtime-endpoint
args deprecated in kubelet), this annotation and args are used to specify the CRI socket endpoint on each node that the kubelet uses to communicate with the container runtime.Add
kubelet-instance-config.yml
locally to store container runtime interface (CRI) sockets, and inkubeadm init
,join
andupgrade
, override the global kubelet configuration throughkubelet-instance-config.yml
.More detailed design at: https://hackmd.io/@r2Yq-PVoRcK2OaGypnwPMg/rJFChACCp/edit
Tasks
The text was updated successfully, but these errors were encountered: