What is the primary use case of a ClusterIP service in Kubernetes?

What is the primary use case of a ClusterIP service in Kubernetes?

• A. To establish a service with an internal IP address, reachable only within the cluster.
• B. To expose a service on an external load balancer visible from outside the cluster.
• C. To route traffic to external resources outside the cluster.
• D. To create a DNS entry that points to a single, cluster-wide IP.

Answer: (A)

A ClusterIP service provides a stable, internal address for a set of pods behind the service. Kubernetes assigns a virtual IP from the cluster’s service IP range, and kube-proxy routes traffic sent to that IP to one or more backend pods that match the service’s selector. This internal IP is reachable only from within the cluster, so the service remains inaccessible from outside by default. Inside the cluster, clients can use the service name (via DNS, such as my-service.namespace.svc.cluster.local) to reach it, benefiting from internal load balancing across the pods. If you need external access, you’d choose a different method (like a LoadBalancer or NodePort) or an Ingress, which is why the internal-only nature of ClusterIP is the key point.

A ClusterIP service provides a stable, internal address for a set of pods behind the service. Kubernetes assigns a virtual IP from the cluster’s service IP range, and kube-proxy routes traffic sent to that IP to one or more backend pods that match the service’s selector. This internal IP is reachable only from within the cluster, so the service remains inaccessible from outside by default. Inside the cluster, clients can use the service name (via DNS, such as my-service.namespace.svc.cluster.local) to reach it, benefiting from internal load balancing across the pods.

If you need external access, you’d choose a different method (like a LoadBalancer or NodePort) or an Ingress, which is why the internal-only nature of ClusterIP is the key point.