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

Skip display name ServiceInsight #9729

Open
jakubdyszkiewicz opened this issue Mar 26, 2024 · 3 comments · May be fixed by #11508
Open

Skip display name ServiceInsight #9729

jakubdyszkiewicz opened this issue Mar 26, 2024 · 3 comments · May be fixed by #11508
Assignees
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it
Milestone

Comments

@jakubdyszkiewicz
Copy link
Contributor

Description

We should not show display name label in ServiceInsight

@jakubdyszkiewicz jakubdyszkiewicz added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Mar 26, 2024
@jakubdyszkiewicz jakubdyszkiewicz 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 Apr 2, 2024
@lahabana lahabana added this to the 2.8.x milestone Apr 10, 2024
@lahabana lahabana modified the milestones: 2.8.x, 2.9.x Jun 3, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Sep 2, 2024
Copy link
Contributor

github-actions bot commented Sep 2, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz removed the triage/stale Inactive for some time. It will be triaged again label Sep 2, 2024
@Icarus9913
Copy link
Contributor

Icarus9913 commented Sep 18, 2024

It's the API server response, not kubectl.

The label "kuma.io/display-name": "all-services-default" comes from the ServiceInsight resource, however in this API it shouldn't exist because the weird value all-services-default.
So, let's just remove this label.

$ curl http://localhost:5681/meshes/default/service-insights/demo-app_kuma-demo_svc_5000
{
 "type": "ServiceInsight",
 "mesh": "default",
 "name": "demo-app_kuma-demo_svc_5000",
 "creationTime": "2024-09-18T07:54:45Z",
 "modificationTime": "2024-09-18T07:54:45Z",
 "labels": {
  "kuma.io/display-name": "all-services-default"
 },
 "status": "online",
 "dataplanes": {
  "total": 1,
  "online": 1
 },
 "addressPort": "demo-app_kuma-demo_svc_5000.mesh:80"
}

@lahabana lahabana added kind/bug A bug and removed kind/feature New feature labels Sep 20, 2024
@lahabana lahabana modified the milestones: 2.9.x, 2.10.x Sep 20, 2024
@Icarus9913 Icarus9913 linked a pull request Sep 22, 2024 that will close this issue
5 tasks
@Icarus9913
Copy link
Contributor

By the way, this only happens in k8s mode.

For universal mode it doesn't own that label in Meta

root@aac9440b67fb:~# curl http://localhost:5681/service-insights
{
 "total": 1,
 "items": [
  {
   "type": "ServiceInsight",
   "mesh": "default",
   "name": "backend",
   "creationTime": "2024-09-22T09:16:01.584481576Z",
   "modificationTime": "2024-09-22T09:16:02.586096122Z",
   "status": "online",
   "dataplanes": {
    "total": 1,
    "online": 1
   },
   "addressPort": "backend.mesh:80",
   "zones": [
    "wk-zone"
   ]
  }
 ],
 "next": null
}
---
root@aac9440b67fb:~# curl http://localhost:5681/meshes/default/service-insights/backend                    
{
 "type": "ServiceInsight",
 "mesh": "default",
 "name": "backend",
 "creationTime": "2024-09-22T09:16:01.584481576Z",
 "modificationTime": "2024-09-22T09:16:02.586096122Z",
 "status": "online",
 "dataplanes": {
  "total": 1,
  "online": 1
 },
 "addressPort": "backend.mesh:80",
 "zones": [
  "wk-zone"
 ]
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants