Skip to content
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

Align generated resource names with GEP 1762 #203

Open
michaelvl opened this issue Jun 13, 2023 · 0 comments
Open

Align generated resource names with GEP 1762 #203

michaelvl opened this issue Jun 13, 2023 · 0 comments
Labels
blueprint enhancement New feature or request

Comments

@michaelvl
Copy link
Collaborator

michaelvl commented Jun 13, 2023

Summary

GEP 1762 states (MUST):

MUST label all generated resources (Service, Deployment, etc) with gateway.networking.k8s.io/metadata.name: my-gateway (where my-gateway is the name of the Gateway resource).
MUST name all generated resources my-gateway-example (-). This is not simply NAME to reduce the chance of conflicts with existing resources.

Motivation

This approach is already being seen with Istio and may improve interoperability.

Note, special concern should be taken with cluster-scoped resource. The current approach of adding namespace to combined name should be retained.

Proposal

Naming as suggested in GEP 1762

@michaelvl michaelvl added enhancement New feature or request blueprint labels Jun 13, 2023
@michaelvl michaelvl added this to the Beta status milestone Jun 14, 2023
@michaelvl michaelvl removed this from the Beta status milestone Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blueprint enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant