DevOps · Flashcard
How does Cilium replace kube-proxy?
- AIt implements Service load-balancing in eBPF — replacing kube-proxy's iptables or IPVS rules entirely
- BIt runs kube-proxy in a sidecar — wrapping the existing component rather than replacing its logic
- CIt moves kube-proxy to the control plane — centralizing the same iptables rules onto the masters
- DIt disables Services altogether — requiring workloads to address pods directly by their IP addresses
Why this is the answer
Cilium can take over Service handling with an eBPF datapath, removing the need for kube-proxy's iptables/IPVS rules. It does not wrap kube-proxy in a sidecar, relocate it to the control plane, or drop Service support — Services keep working, just via eBPF.
Official docs