You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Adding the alpha.service-controller.kubernetes.io/exclude-balancer or node.kubernetes.io/exclude-from-external-load-balancers label to the virtual-kubelet node excludes it from LBs. However, this needs the ServiceNodeExclusion feature gate, which is still alpha in Kubernetes: https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/
Adding the alpha.service-controller.kubernetes.io/exclude-balancer label will make gce-ingress work (not with container-native load balancing, though).
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
The text was updated successfully, but these errors were encountered: