How does Kubernetes's "Container Network Interface" (CNI) plugin architecture enable different networking implementations (e.g. Calico, Cilium, Flannel)?
Correct! Well done.
Incorrect.
The correct answer is B) CNI defines a standard interface between runtimes and network plugins; Kubernetes invokes the configured plugin to set up Pod networking (IPs, routes), letting plugins offer features like policy enforcement or overlay networking without changing core code
Correct Answer
CNI defines a standard interface between runtimes and network plugins; Kubernetes invokes the configured plugin to set up Pod networking (IPs, routes), letting plugins offer features like policy enforcement or overlay networking without changing core code
The CNI specification decouples Kubernetes from specific networking implementations — the kubelet calls the configured CNI plugin to set up each Pod's network namespace, letting operators choose plugins suited to their needs (e.g. Cilium for eBPF-based policy enforcement).