VPC Clusters: My VPC NLB has a zone error and does not update

Your VPC NLB does not update when worker nodes are added or removed from your cluster. Additionally, you see an error similar to the following:

The load balancer was created in zone <zone>. This setting can not be changed.

You included the service.kubernetes.io/ibm-load-balancer-cloud-provider-zone annotation in your VPC NLB configuration and then later changed the specified zone. Changing the annotation to a different zone creates an error and prevents the VPC NLB from updating when worker nodes are added or removed from the cluster. This might cause all network traffic through the load balancer to fail if all the cluster's worker nodes are upgraded and refreshed simultaneously.

You can change the zone specified by the service.kubernetes.io/ibm-load-balancer-cloud-provider-zone annotation for VPC ALBs, but not for VPC NLBs.

Change the service.kubernetes.io/ibm-load-balancer-cloud-provider-zone annotation back to the original zone that was specified when you created the load balancer. If you still need to change the NLB's zone, you must delete, update, and reapply the corresponding Kubernetes LoadBalancer service. For more information, see Changing a load balancer's subnet or zone.