Cilium question:
How are `ClusterIP` type services supposed to be routed when Kube-Proxy is replaced?
Like Service Cluster IP Range must be set in the K8s API server configuration, so the IPAM for that is well outside of Cilium's so... is it supposed to be natively routable? Everything says CIDR overlaps are a no-no.
The pod routing table contains nothing about the ClusterIP, though default routing should be okay `traceroute` shows it hitting the node's cluster IP and then just... nothing.
Is eBPF supposed to be doing DNAT?
I don't get it and I'm so close!
#Cilium #Kubernetes #k8s