CertGrid CertGrid
Hands-on Lab·Certified Kubernetes Application Developer

Service Types End to End

The three Service types on one workload, each proved from the place it is supposed to be reachable from - and an honest look at what a LoadBalancer does on a cluster that has a controller for it and on one that does not.

Services and Networking Guide 35 of 44 Intermediate

Written against the versions above. This cluster runs MetalLB, so EXTERNAL-IP is really allocated. Without a load-balancer controller that column stays Pending, which the last two steps cover.

Four nodes, two replicas. The Pods land on two workers, which is what makes the third node answering its NodePort worth noticing.
Server NameIP AddressOSRolesCPURAMHDD
CKA1001192.168.0.175Ubuntu 26.04 LTSControl Plane Node2 Core4 GB50 GB
CKA1001-NODE01192.168.0.176Ubuntu 26.04 LTSWorker Node2 Core4 GB50 GB
CKA1001-NODE02192.168.0.177Ubuntu 26.04 LTSWorker Node2 Core4 GB50 GB
CKA1001-NODE03192.168.0.178Ubuntu 26.04 LTSWorker Node2 Core4 GB50 GB

Before you start

  1. A workload, and the Service every task starts with

  2. Prove it from inside the cluster

  3. The same Service, as a NodePort

  4. And as a LoadBalancer

  5. What each type kept

Official sources