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 in kubeadm-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 in kubeadm init, join and upgrade, override the global kubelet configuration through kubelet-instance-config.yml.

### Tasks

edit by neolit123:

1.32 alpha

• KEP:
  • kubeadm: Add kubelet instance configuration to configure CRI socket for each node enhancements#4658
  • Add kubelet instance configuration to configure CRI socket for each node #3042
    FG name is NodeLocalCRISocket
• k/k PRs:
  • [Kubeadm] KEP-4656: Add kubelet instance configuration to configure CRI socket for each node kubernetes#128031
• e2e tests
  • Add e2e test for kubelet instance config #3126
  • kubeadm: add e2e test for kubelet instance config test-infra#33807
• k/website changes:
  • kubeadm: add 1.32 documentation website#48408

1.33 alpha

• k/k PRs:
  • [NodeLocalCRISocket]: Remove container-runtime-endpoint flag when kubeadm upgrade kubernetes#129278
  • [NodeLocalCRISocket]: remove kubeadm.alpha.kubernetes.io/cri-socket annotation when kubeadm upgrade kubernetes#129279

1.34 beta

• k/k PRs:
  • kubeadm: Graduate NodeLocalCRISocket Feature gate to beta kubernetes#131981
• e2e tests
  • Add beta stage test for NodeLocalCRISocket feature gate #3212 (comment)
• k/website changes:
  • Add documentation for promoting the NodeLocalCRISocket to Beta website#51503