Kubernetes Services and Networking

Explain the different types of Kubernetes Services (ClusterIP, NodePort, LoadBalancer) and when to use each.

Kubernetesintermediate

// interview question

Explain the different types of Kubernetes Services (ClusterIP, NodePort, LoadBalancer) and when to use each.

Sample answer

ClusterIP (default) exposes the service on an internal IP, accessible only within the cluster - use for internal communication between pods. NodePort exposes the service on each node's IP at a static port (30000-32767) - use for development or when you manage your own load balancer. LoadBalancer provisions an external load balancer (in cloud environments) - use for production external traffic. Ingress is not a service type but a separate resource for HTTP/HTTPS routing with a single entry point.

Why this matters

Kubernetes networking is essential for connecting microservices and exposing applications. Understanding service types helps architects design secure, scalable systems and troubleshoot connectivity issues efficiently.

Code examples

Kubernetes Service types

yaml

# ClusterIP (internal only)
apiVersion: v1
kind: Service
metadata:
  name: backend-service
spec:
  type: ClusterIP
  selector:
    app: backend
  ports:
    - port: 80
      targetPort: 8080
---
# LoadBalancer (external traffic)
apiVersion: v1
kind: Service
metadata:
  name: frontend-service
spec:
  type: LoadBalancer
  selector:
    app: frontend
  ports:
    - port: 80
      targetPort: 3000

Common mistakes to avoid

Using LoadBalancer for every service (costly and unnecessary)
Confusing targetPort with port
Not understanding that NodePort opens ports on ALL nodes

Likely follow-ups

What is the difference between port, targetPort, and nodePort?
How does kube-proxy handle service traffic?
When would you use an Ingress instead of a LoadBalancer service?

Answer out loud first, then check yourself against the model answer.

Practice all Mid-Level questions More Kubernetes questions

#kubernetes#networking#services#ingress#load-balancing

Also worth your time on this topic

Article

Ingress-NGINX Is Retired: A Real Migration to Gateway API With ingress2gateway 1.0

In March 2026 the Kubernetes project retired ingress-nginx with no replacement waiting in the wings. Roughly half of all clusters still run it. This post is the migration that does not involve a flag day: how to inventory your annotations, what ingress2gateway 1.0 translates and what it silently drops, the side-by-side cutover pattern with the actual PromQL, and how to pick between Envoy Gateway, kgateway, Cilium Gateway, and Istio.

Interview

Service Mesh Concepts

What is a service mesh and when would you implement one? Explain the sidecar pattern.

mid

Checklist

Argo CD Multi-Environment Repository Structure Checklist

How to organize your Git repositories when running Argo CD across dev, staging, and production. Covers folder layout, app-of-apps, ApplicationSets, secrets, RBAC, and promotion flow.

60-90 minutes

Kubernetes Services and Networking

More Kubernetes interview questions

Also worth your time on this topic

Ingress-NGINX Is Retired: A Real Migration to Gateway API With ingress2gateway 1.0

Service Mesh Concepts

Argo CD Multi-Environment Repository Structure Checklist