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

grafana shows the old naming pattern in the source service #12510

Open
johncowen opened this issue Jan 10, 2025 · 4 comments
Open

grafana shows the old naming pattern in the source service #12510

johncowen opened this issue Jan 10, 2025 · 4 comments
Labels
kind/design Design doc or related triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@johncowen
Copy link
Contributor

What happened?

When using grafana (at least) the old naming pattern is shown for Source Service whilst the Destination Service uses the new "MeshService" naming pattern.
@johncowen johncowen added kind/bug A bug triage/pending This issue will be looked at on the next triage meeting labels Jan 10, 2025
@lahabana
Copy link
Contributor

What's the old naming pattern?

@johncowen
Copy link
Contributor Author

_svc_<port> from what I understood

@jakubdyszkiewicz
Copy link
Contributor

What's the old naming pattern?
kuma.io/service

It's kind of expected, but if we want to move from using kuma.io/service we need to figure out how to replace it.

@lahabana
Copy link
Contributor

Right if it's source we need to have the workload identity we've been talking about in the past right?

@bartsmykla bartsmykla added triage/accepted The issue was reviewed and is complete enough to start working on it kind/design Design doc or related and removed triage/pending This issue will be looked at on the next triage meeting kind/bug A bug labels Jan 13, 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
4 participants
@johncowen @lahabana @jakubdyszkiewicz @bartsmykla