Kinda similar to #4717 but for Calico services themselves. I noticed that all services in calico-system are set to SingleStack even though our cluster runs in a dual stack configuration. Personally, I would love if the operator would just detect this automatically and set the IP family policy to PreferDualStack, however controlling this manually with some field in the various CRDs might be better? The end goal should be that all services are running in dual stack configuration. For us, the current list of services are:
$ kubectl --namespace calico-system get svc --selector app.kubernetes.io/managed-by=tigera-operator
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
calico-kube-controllers-metrics ClusterIP None <none> 9094/TCP 329d
calico-typha ClusterIP 10.24.81.35 <none> 5473/TCP 329d
calico-typha-metrics ClusterIP 10.24.106.234 <none> 9093/TCP 292d
calico-webhooks ClusterIP 10.24.83.114 <none> 443/TCP 14d
goldmane ClusterIP 10.24.66.1 <none> 7443/TCP 329d
whisker ClusterIP 10.24.80.130 <none> 8081/TCP 329d
The calico-kube-controllers-metrics service can be ignored since it uses clusterIP: None and gets no IP address either way.
Kinda similar to #4717 but for Calico services themselves. I noticed that all services in
calico-systemare set toSingleStackeven though our cluster runs in a dual stack configuration. Personally, I would love if the operator would just detect this automatically and set the IP family policy toPreferDualStack, however controlling this manually with some field in the various CRDs might be better? The end goal should be that all services are running in dual stack configuration. For us, the current list of services are:The
calico-kube-controllers-metricsservice can be ignored since it usesclusterIP: Noneand gets no IP address either way.