Couldn't find ipfamilies for headless service
Issue
- The
kube-controller-manager
shows the below log message.
I0810 15:45:32.467665 1 utils.go:413] couldn't find ipfamilies for headless service: service-name/service-name-webapi. This could happen if controller manager is connected to an old apiserver that does not support ip families yet. EndpointSlices for this Service will use IPv4 as the IP Family based on familyOf(ClusterIP:10.x.x.x).
- Can Cluster IP be used in headless service definition?
Environment
- Red Hat OpenShift Container Platform(RHOCP)
- 4.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.