Which service type uses an internal IP accessible only within the cluster?

Which service type uses an internal IP accessible only within the cluster?

• A. Ingress
• B. ExternalName
• C. ClusterIP
• D. NodePort

Answer: (C)

ClusterIP creates a stable virtual IP that exists only inside the Kubernetes cluster. Pods within the cluster can reach the service using this IP or its DNS name, but it is not exposed outside the cluster, making it the default choice for internal communication between components. Ingress is meant to handle external HTTP(S) traffic via an Ingress controller, ExternalName maps to an external DNS name rather than providing a cluster IP, and NodePort exposes the service on a port on every node to allow external access.

ClusterIP creates a stable virtual IP that exists only inside the Kubernetes cluster. Pods within the cluster can reach the service using this IP or its DNS name, but it is not exposed outside the cluster, making it the default choice for internal communication between components. Ingress is meant to handle external HTTP(S) traffic via an Ingress controller, ExternalName maps to an external DNS name rather than providing a cluster IP, and NodePort exposes the service on a port on every node to allow external access.