cloud-provider-aws icon indicating copy to clipboard operation
cloud-provider-aws copied to clipboard

External CCM without the --node-ip kubelet flag results in pod IPs as the node addresses

Open tzneal opened this issue 1 year ago • 3 comments

What happened:

When using kubelet with the external CCM and not using the --node-ip flag, pod IPs were added to the node.status.addresses by the CCM which caused logs/exec to fail.

What you expected to happen:

I did not expect to see pod IPs in the node addresses list.

How to reproduce it (as minimally and precisely as possible):

Start kubelet with the external CCM and without the --node-ip flag.

Or, for any running node started with the --node-ip flag, remove the alpha.kubernetes.io/provided-node-ip annotation from the node object. Within a few minutes you will see the pod IPs added to the node status.

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): Server Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.4-eks-2d98532", GitCommit:"3d90c097c72493c2f1a9dd641e4a22d24d15be68", GitTreeState:"clean", BuildDate:"2023-07-28T16:51:44Z", GoVersion:"go1.20.6", Compiler:"gc", Platform:"linux/amd64"}
  • Cloud provider or hardware configuration: EKS 1.27
  • OS (e.g. from /etc/os-release): AL2 AMI
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:

/kind bug

tzneal avatar Sep 12 '23 02:09 tzneal