Repository navigation
Creating GCE external load balancer fails #106
Description
The GCE cloud provider in k8s does not like the fact that there's no cloud instance called virtual-kubelet:
default 3s Normal EnsuringLoadBalancer service/nginx Ensuring load balancer
default 3s Warning CreatingLoadBalancerFailed service/nginx Error creating load balancer (will retry): failed to ensure load balancer for service default/nginx: instance not found
Whether we use host network mode or not does not matter though. It's hard-coded in the GCE cloud plugin to list all nodes and bail if any of them is not a GCE VM instance: https://github.com/kubernetes/legacy-cloud-providers/blob/master/gce/gce_loadbalancer_external.go#L59-L62
Activity
ldx commentedon May 31, 2020
Adding the
alpha.service-controller.kubernetes.io/exclude-balancerornode.kubernetes.io/exclude-from-external-load-balancerslabel to the virtual-kubelet node excludes it from LBs. However, this needs theServiceNodeExclusionfeature gate, which is still alpha in Kubernetes: https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/Creating an alpha cluster in GKE will enable the feature gate, however, alpha clusters are not supported for production workloads: https://cloud.google.com/kubernetes-engine/docs/concepts/alpha-clusters
ldx commentedon Jun 1, 2020
ServiceNodeExclusionwill graduate to beta and will be on by default in 1.19: kubernetes/kubernetes@2369ef0ldx commentedon Jun 1, 2020
Adding the
alpha.service-controller.kubernetes.io/exclude-balancerlabel will make gce-ingress work (not with container-native load balancing, though).