☁️ Free practice test question from: KCNA (KCNA)

Imagine you have a cluster with lots of containers (called "pods" in Kubernetes) that need to talk to each other. These pods are constantly being created and destroyed as your application scales or updates. Each time a pod changes, it gets a new IP address.

This creates a challenge: how do other pods find and connect to the right pods when their addresses keep changing?

Think of a ClusterIP Service like a virtual phone operator inside your Kubernetes cluster. When you want to call a department in a big company, you don't need to know each person's direct number - you just call the department's main number, and the operator connects you to whoever is available.

#####

A) NodePort Service: This is just a service type that exposes the service on each node's IP at a static port. It still relies on the same underlying endpoint tracking mechanism as ClusterIP.

C) LoadBalancer Service: This builds on top of NodePort and provisions an external load balancer, but again uses the same endpoint tracking as ClusterIP.

D) IP Address Management (IPAM) Plugins: These are responsible for allocating IP addresses to pods as they're created, but don't handle tracking those IPs for service discovery purposes.