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.

Sign up for GitHub

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

Jump to bottom

Formalize the names of built-in gateway resources - listeners, clusters etc. #12148

Open
bartsmykla opened this issue Dec 2, 2024 · 0 comments
Open

Formalize the names of built-in gateway resources - listeners, clusters etc. #12148

bartsmykla opened this issue Dec 2, 2024 · 0 comments
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@bartsmykla
Copy link
Contributor

Description

xref. kumahq/kuma-gui#3236

We should formalize the names of built-in gateway resources. Currently there is no differentiation in the names of these resources between resources for regular services and gateways

We should think about impact on users relying on current names in their MeshProxyPatches

  • could be a feature flag
@bartsmykla bartsmykla added triage/accepted The issue was reviewed and is complete enough to start working on it kind/feature New feature labels Dec 2, 2024
@bartsmykla bartsmykla mentioned this issue Dec 2, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bartsmykla