Q: What is the difference between ClusterIP, NodePort, and LoadBalancer service types?
- ClusterIP — only accessible inside the cluster. Default type. Used for internal service-to-service communication.
Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
- ClusterIP — only accessible inside the cluster. Default type. Used for internal service-to-service communication.
- NodePort — opens a port (30000–32767) on every node. Traffic to
reaches the service. Used for dev/testing or when you manage your own load balancer.: - LoadBalancer — creates a cloud load balancer (AWS ELB, GCP LB) and assigns an external IP. Used in production to expose services to the internet. Only works in cloud environments.
Remediation & Permanent Safeguards
Execute the resolution runbook and verify workload health:
- ClusterIP — only accessible inside the cluster. Default type. Used for internal service-to-servic...
- NodePort — opens a port (30000–32767) on every node. Traffic to : reaches the service. Used for d...
- LoadBalancer — creates a cloud load balancer (AWS ELB, GCP LB) and assigns an external IP. Used i...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
-
Configuring Service selector labels that mismatch underlying Pod manifest metadata when configuring difference ClusterIP NodePort
A typo in
spec.selectorcauses the Service endpoints list (kubectl get endpoints) to remain empty, resulting in503 Service Unavailableor timeouts. -
Omitting explicit ingressClassName specifications when running multiple ingress controllers when configuring difference ClusterIP NodePort
Without an explicit
ingressClassName, ingress resources are either ignored or picked up unpredictably by competing controllers. -
Depleting worker node subnet IP address allocations under VPC CNI or Azure CNI when configuring difference ClusterIP NodePort
Direct VPC pod networking allocates real subnet IPs; failing to monitor IP pools causes new pods to stay stuck indefinitely in
ContainerCreating. - Attempting network triage without inspecting kubectl describe service and EndpointSlice resources when configuring difference ClusterIP NodePort Verifying EndpointSlice population immediately determines whether a connectivity failure is caused by pod labeling, readiness probes, or routing.