GCE resource leak with v1 frontend namer

[skmatti]

v1 frontend namer leaks GCE loadbalancer forntend resources for the following ingress names,
Examples: ingress--1, ingress--2
Basically, when there exist two consecutive hyphens in namespace or name.

Few of the other cases are (in <namespace>/<name> format),
namespace-/ing1, namespace/-ing2

The current workflow for v1 frontend namer parses load-balancer name incorrectly.
For example,
URL map k8s-um-default-my--ingress--260743b4176675c7 is parsed as default-my-260743b4176675c7 which should have been parsed as default-my--ingress-260743b4176675c7.

[rramkumar1]

@skmatti What is the status of this issue?

[skmatti]

Discussed with @freehan and decided that we are not going to fix this special case. May be this should be marked as one of the known issues.

Also, v1.8.1 and above will not run into this issue.

[fejta-bot]

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

[skmatti]

/close

[k8s-ci-robot]

@skmatti: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[bowei]

@skmatti did you update the known issues if this is closed?