Uploaded November 2026 | Updated November 2026, 1 day ago
Why does a Kubernetes LoadBalancer service stay stuck on pending, and how do you give it a real external IP? This DevCentral video picks up from our earlier look at Kubernetes service types and explains what happens behind the scenes.
What this video covers:
- How the cloud controller manager on AWS, Azure and Google Cloud watches for LoadBalancer services, provisions a cloud load balancer, and writes its address back into the service as the external IP.
- Why the same service stays on pending in an on-premises data center, where no cloud controller exists to create the load balancer.
- How MetalLB fills the gap inside the cluster, using a pool of IP addresses from your own network.
- The difference between MetalLB layer 2 mode, where one node answers for the IP, and BGP mode, where your routers can spread traffic across several nodes.
- How a dedicated external load balancer, kept in step with Kubernetes by a controller, watches services and pods and sends traffic directly to the pods.
- Three questions to help you choose: where the IP lives, how traffic reaches the pods, and who owns it.
Who this is for: platform engineers, cluster operators, and network teams deciding how to expose Kubernetes services outside the cloud.
The next video covers Ingress, which puts many apps behind a single entry point.
▬▬▬ ABOUT DEVCENTRAL ▬▬▬
We're DevCentral: the how of F5, since 2003. A community of engineers, architects, and IT folks pushing each other forward, one hard-won answer at a time. We dig in, tackle the hard stuff, figure out what actually works, and share what we learn.
Keep going:
Forums, articles, CodeShare: community.f5.com
LinkedIn: linkedin.com/showcase/f5-devcentral
X: https://x.com/devcentral
The DevCentral advocates behind the videos:
Alessandro Fael Garcia → linkedin.com/in/alessfg · github.com/alessfg
Buu Lam → linkedin.com/in/buulam · https://x.com/buulam
Chase Abbott → linkedin.com/in/chaseabbott1
Jason Rahm → linkedin.com/in/jrahm · https://x.com/jasonrahm
Marko Sluga → linkedin.com/in/markosluga
Scott McAllister → linkedin.com/in/stmcallister
Why does a Kubernetes LoadBalancer service stay stuck on pending, and how do you give it a real external IP? This DevCentral video picks up from our earlier look at Kubernetes service types and explains what happens behind the scenes.
What this video covers:
- How the cloud controller manager on AWS, Azure and Google Cloud watches for LoadBalancer services, provisions a cloud load balancer, and writes its address back into the service as the external IP.
- Why the same service stays on pending in an on-premises data center, where no cloud controller exists to create the load balancer.
- How MetalLB fills the gap inside the cluster, using a pool of IP addresses from your own network.
- The difference between MetalLB layer 2 mode, where one node answers for the IP, and BGP mode, where your routers can spread traffic across several nodes.
- How a dedicated external load balancer, kept in step with Kubernetes by a controller, watches services and pods and sends traffic directly to the pods.
- Three questions to help you choose: where the IP lives, how traffic reaches the pods, and who owns it.
Who this is for: platform engineers, cluster operators, and network teams deciding how to expose Kubernetes services outside the cloud.
The next video covers Ingress, which puts many apps behind a single entry point.
▬▬▬ ABOUT DEVCENTRAL ▬▬▬
We're DevCentral: the how of F5, since 2003. A community of engineers, architects, and IT folks pushing each other forward, one hard-won answer at a time. We dig in, tackle the hard stuff, figure out what actually works, and share what we learn.
Keep going:
Forums, articles, CodeShare: community.f5.com
LinkedIn: linkedin.com/showcase/f5-devcentral
X: https://x.com/devcentral
The DevCentral advocates behind the videos:
Alessandro Fael Garcia → linkedin.com/in/alessfg · github.com/alessfg
Buu Lam → linkedin.com/in/buulam · https://x.com/buulam
Chase Abbott → linkedin.com/in/chaseabbott1
Jason Rahm → linkedin.com/in/jrahm · https://x.com/jasonrahm
Marko Sluga → linkedin.com/in/markosluga
Scott McAllister → linkedin.com/in/stmcallister










