Service Type LoadBalancer¶
A service of type LoadBalancer is the simplest and the fastest way to
expose a service inside a Kubernetes cluster to the external world. You
only need to specify the service type as type=LoadBalancer in the
service definition.
Services of type LoadBalancer are natively supported in Kubernetes
deployments. For services of the type LoadBalancer, the BIG-IP Next CIS
controller deployed inside the Kubernetes cluster reads service type LB
and creates the corresponding LTM virtuals on the BIG-IP Next that load
balance the incoming traffic to the Kubernetes cluster.
Service Type LoadBalancer Annotations¶
| Annotation | Required | Description | Example |
|---|---|---|---|
| cis.f5.com/ipamLabel | Mandatory | Specify the ipamLabel if you are using the FIC controller to configure the IP addresses. See How F5 IPAM Controller works. | |
| cis.f5.com/ip | Mandatory | Specify the ip address for the LTM virtual server. | |
| cis.f5.com/health | Optional |
|
Note
If both the cis.f5.com/ipamLabel and cis.f5.com/ip annotations are
provided, then the cis.f5.com/ip will be given priority and LTM
virtual will be created using the IP address provided
by cis.f5.com/ip.
Note
To provide feedback on Container Ingress Services or this documentation, please file a GitHub Issue.