-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow naming NEG when ingress: true #1727
Comments
/kind feature |
+1 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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. |
Hi!
I currently use annotation
"cloud.google.com/neg"
(NEGAnnotationKey
https://github.com/kubernetes/ingress-gce/blob/master/pkg/annotations/service.go#L39-L47) withingress: true
to automatically create network endpoint groups. It works incredibly well.I want to set a custom name to NEGs. I saw in GCP documentation that it's possible, but that means dropping
ingress: true
, which I don't want to do 😢.Is there any plan to support this?
If I can bring any help, I'd be happy to.
The text was updated successfully, but these errors were encountered: