Internal Load Balancing
This section continues from the previous section - make sure you do the tutorial in sequence.
ServiceIn-Cluster Load Balancer
A Kubernetes Service acts as an internal L4 load balancer only accessible from within the same Kubernetes Cluster. See the Service section for more information.
Internal Network Load Balancer
The setup of the Internal Network Load Balancer is similar to the External Network Load Balancer, but with an additional annotation.
Service YAML
In k8s/service.yaml
, use the cloud.google.com/load-balancer-type
annotation to mark the service to use the Internal Network Load Balancer:
Internal Static IP
You can assign an internal static IP address to the Network Load Balancer.
Reserve a regional static IP address:
See the reserved IP address:
Update the k8s/service.yaml
to pin the Load Balancer IP address:
Internal HTTP(s) Load Balancer
The setup of the Internal Network Load Balancer is similar to the External HTTP(s) Load Balancer, but with an additional annotation.
Service YAML
In the k8s/service.yaml
, use the cloud.google.com/neg
annotation to enable Network Endpoint Group (NEG) in order to use container-native load balancing:
Ingress YAML
Create a Kubernetes Ingress configuration that will create the HTTP Load Balancer. Create a k8s/ingress.yaml
, but also use kubernetes.io/ingress.class
annotation to indicate this is an Internal HTTP(s) Load Balancer
Last updated