How does Kubernetes service discovery work?
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of Kubernetes conventions, runtime behavior, and memory/performance considerations.
02
Evaluation Criteria
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Comprehensive Model Answer
Verified Solution
Kubernetes gives stable access to moving Pods through Services and DNS.
- A Service selects Pods by label and gets a stable virtual IP, the ClusterIP, and a DNS name.
- kube-proxy programs iptables or IPVS rules on each node so traffic to the ClusterIP is load-balanced to healthy endpoints.
- Endpoints, or EndpointSlices, are updated by the control plane as Pods become ready or are removed.
- CoreDNS resolves service names in the form service.namespace.svc.cluster.local. Short names work within the same namespace.
Service types:
- ClusterIP: internal only, the default.
- NodePort: exposes a port on every node.
- LoadBalancer: provisions an external load balancer.
- ExternalName: aliases an external DNS name.
kubectl get svc,endpoints
nslookup api.default.svc.cluster.local
Headless Services with clusterIP set to None return Pod IPs directly, which is useful for StatefulSets.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.