For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Double Trouble: Multiple Controllers Handling the Same Kubernetes LoadBalancer Service

This is a summary of a confusing problem I saw recently. It also reminds us of two best practices: use the LoadBalancerClass field always and deploy with automation.   The problem statement A c...
Updated Aug 06, 2025
Version 16.0
cloud
devops
MichaelOLeary's avatar
Icon for Employee rankEmployee
I'm a Solution Architect at F5. Over the years I've become an expert in Kubernetes and cloud architectures. I publish articles and blog posts to share as much knowledge as possible. I love hanging out with colleagues and customers, so reach out any time!
View Profile
JackF's avatar
Icon for Employee rankEmployee
Joined January 08, 2012
View Profile
Nikoolayy1's avatar
Nikoolayy1
Icon for MVP rankMVP
Nov 11, 2025

This is great! As many k8s deployments may have things like MetalLB before moving to F5 CIS and this way the transition could be easy ! Also using CIS with Custom Resource CRD VirtualServer is another way to bypass using the Default Load Balancer Service.