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

MADR on naming "internal" Envoy resources #13266

Open
lobkovilya opened this issue Mar 28, 2025 · 0 comments
Open

MADR on naming "internal" Envoy resources #13266

lobkovilya opened this issue Mar 28, 2025 · 0 comments
Labels
kind/design Design doc or related triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@lobkovilya
Copy link
Contributor

Description

Some resources in Envoy don't correlate with the real resources in the store. That's why we can't use KRI formatted name for these resources. We need to revisit names for the following resources:

  • Secrets
  • Internal Listeners and Clusters
  • Default routes (when there are no MeshHTTPRoute/MeshTCPRoute policies)
  • MeshPassthrough resources
@lobkovilya lobkovilya added kind/feature New feature triage/pending This issue will be looked at on the next triage meeting kind/design Design doc or related and removed kind/feature New feature labels Mar 28, 2025
@lukidzi lukidzi added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/design Design doc or related 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
2 participants
@lobkovilya @lukidzi