Member-only story
[CKNE Exam Prep] 1.1 — Installing and Configuring CNI Plugins
Kubernetes relies on CNI for the underlying Networking.
Kubernetes without CNI
- the nodes would be ‘Not Ready’ status
- Some pods would be Running, some Pending
- The pods running, they’re running on ‘hostNetwork’, meaning they’re running on the Node IP itself, not on Cluster Pod Network.
Try it yourself — Install CNI
- Setup Kubernetes with
kubeadm init - Before installing CNI, check
kubectl get nodekubectl get po -owide -Akubectl run po --image=nginxsudo ls /etc/cni/net.dsudo ls /opt/cni/bin
3. For observation, create a file sudo touch /etc/cni/net.d/test.conflist
4. Install Cilium CNI (the de facto CNI for CKNE exam), observe the above commands again
What’re the differences? Share in the comment below :)
Note: You could also observe ‘pre-CNI state’ by going to killercoda playgrounds > Kubernetes playground, then run cilium uninstall and sudo rm /etc/cni/net.d/, the nodes would be ‘Not Ready’ afterwards.


![[Lab] Incident Response with AI Agent in Kubernetes](https://webproxy.poorya-velaei-d67.workers.dev/https://miro.medium.com/v2/resize:fit:1358/format:webp/1*DCBTYOH-chEp0PX2Y0p4Ew.png)

![[Kubernetes Lab] Understanding Gateway API Inference Extension](https://webproxy.poorya-velaei-d67.workers.dev/https://miro.medium.com/v2/resize:fit:1358/format:webp/1*RAS3t49RQ3clVmzKRoLyYQ.png)





