[GLBC] Changing front-end configuration does not remove unnecessary target proxies/ssl-certs about ingress-gce HOT 13 CLOSED

It is still relevant, I just hit this today. /remove-lifecycle stale

from ingress-gce.

Hitting this on v1.1.1

/remove-lifecycle stale

from ingress-gce.

Same issue here, changed to HTTPS only and the HTTP frontend was not deleted.
I deleted the HTTP frontend manually from the LB and that did not seem to have any side-effects on the traffic.

from ingress-gce.

/lifecycle frozen

from ingress-gce.

From @nicksardo on April 21, 2017 19:7

No deletion/cleanup happens when removing the TLS section or pre-shared cert annotation. Will rename this to be more general.

from ingress-gce.

From @nicksardo on April 24, 2017 18:41

Furthermore, if you disable TLS on an active ingress, then delete the ingress resource, the controller will fail to destroy resources. It doesn't try deleting the https forwarding rule or https target proxy, which means the URL map is still used.

from ingress-gce.

From @montanaflynn on August 7, 2017 23:3

Any updates on this? We have a production ingress and are looking for a workaround.

from ingress-gce.

From @nicksardo on August 7, 2017 23:19

@montanaflynn There's no fix yet.

You should be able to delete the HTTP forwarding rule and target proxy manually in the GCP Console. Highly recommend duplicating the issue in a test cluster and trying it out first.

from ingress-gce.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

from ingress-gce.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from ingress-gce.

Bump. Had to delete ingress, remove compute forwarding rule, wait, apply ingress. kubectl replace of ingress did not work.

from ingress-gce.

Still happening, added kubernetes.io/ingress.allow-http: "false" and the HTTP Frontend was not deleted.

Cleaned manually after adding the annotation by updating the Ingress Load Balancer removing the HTTP Frontend. Eventually, the HTTP Target Proxy was deleted by GCP.

from ingress-gce.

Until this reaches production please document the manual cleanup required (or link to this bug) at https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#disabling_http.

from ingress-gce.