ClusterIP vs NodePort vs LoadBalancer
WHAT IT TESTS: Service type selection. OUTLINE: ClusterIP for internal-only access; NodePort opens a port on every node for basic external reach; LoadBalancer provisions a cloud load balancer for production external traffic.
WHAT IT TESTS: Whether you can match Service type to exposure needs. ANSWER OUTLINE: ClusterIP is the default and exposes the Service only inside the cluster, ideal for internal microservice-to-microservice calls. NodePort opens a static port on every node's IP and forwards to the Service, useful for dev, on-prem, or behind your own load balancer. LoadBalancer provisions an external cloud load balancer pointing at the Service, the standard way to expose production apps to the internet. Each type builds on the one below it.
Read the original → interview
- #kubernetes
- #services
- #clusterip
- #nodeport
- #loadbalancer
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.