[GLBC] LB garbage collection orphans named ports in instance groups

[nicksardo]

The GLBC does not remove the named port from an instance group when a backend is being deleted.

If users are frequently created/deleting services and ingresses, instance groups will become polluted with old node ports. Eventually, users will hit a max limit.

Exceeded limit 'MAX_DISTINCT_NAMED_PORTS' on resource 'k8s-ig--aaaaaaaaaaaa'

Temporary workaround

region=us-central1
cluster_id=$(kubectl get configmaps ingress-uid -o jsonpath='{.data.uid}' --namespace=kube-system)
ports=$(gcloud compute backend-services list --global --format='value(port,port)' |  xargs printf 'port%s:%s,')
for zone in b c f; do
  gcloud compute instance-groups unmanaged set-named-ports k8s-ig--$cluster_id --zone=$region-$zone --named-ports=$ports
done

Modify the region and list of zone suffix in the script.

[nicksardo]

Requires kubernetes/kubernetes#46457

[porridge]

I see that the dependency was merged a week ago. Is there a plan/ETA for this one?

[nicksardo]

@porridge I'm waiting on one more PR to merge before we can update this repo's vendored dependencies.

I expect to have a fix in for the next release of GLBC, but there's no ETA for that just yet.

[pawloKoder]

Any update on this issue?

[G-Harmon]

Hi, I'm starting to work on this now, as my first Kubernetes fix.

[bowei]

This issue was moved to kubernetes/ingress-gce#43