Feature Request: Name GCP resources better

[ashi009]

It's annoying to see a backend being referred as k8s-be-31073--d4ff5a71b6e25bd6, or an instance group being named as k8s-ig--d4ff5a71b6e25bd6. All these names are totally meaningless on the GKE console.

Is it possible to give them some more meaningful names?

[mayansalama]

Piggybacking onto this, it would be useful if there were a way to configure the name of the backend-service created by the Ingress.

I've been looking into using IAP for authentication, however getting user ID in GKE requires the backend service ID, which is a bit of a chicken and egg problem. Right now getting it working properly requires either redeploying, dynamic config, or looking up the service ID live - being able to name the backend service ID would make this somewhat easier.

[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

[rramkumar1]

/remove-lifecycle stale
/lifecycle frozen

[rramkumar1]

@skmatti CC'ing you since you are looking into this.

[shpml]

Is there any progress on this? Trying to view metrics and create alerts based on response codes with a backend being referred as above isn't very informative. Ideally I'd like to see the k8's service name.

[swetharepakula]

Closing as this issue hasn't had any comments in over a year. The newer GCP resources like NEGs do have service names added into the name.