Why Daemonset pod will be allocated with ip which is exactly same as node ip

Question

I am recently maintaining a GKE cluster(data plane v2) and notice that in the namespace of kube-system, there are a lot of pods whose ip is same as the node ip. Is it intended? I understand that daemonset manages things at node level but still I can recall there is a k8s doc saying each pod should be assigned an unique IP.

Answer 1

In general each pod will have its own ip address, If you are getting the same IP for multiple pods it can create an issue unless the pods are networking controller such as anetd pods.

From the official documentation:

GKE deploys the GKE Dataplane V2 controller as a DaemonSet named anetd to each node in the cluster. anetd interprets Kubernetes objects and programs network topologies in eBPF. The anetd Pods run in the kube-system namespace.

So these types of pods may have the same ip as nodes which will not be an issue.