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

Consider combining name/namespace/zone together across the GUI #2978

Open
johncowen opened this issue Sep 19, 2024 · 0 comments
Open

Consider combining name/namespace/zone together across the GUI #2978

johncowen opened this issue Sep 19, 2024 · 0 comments
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Milestone

Comments

@johncowen
Copy link
Contributor

johncowen commented Sep 19, 2024

Description

There are many places where we show the user a name of say tcp-service, which is possibly not a unique name for the service. Its fully qualified name is more likely to be a combination of name/zone/namespace.

As these properties are all related to "providing a unique identifier" for the resource. It might be better to use a visually combined display for these properties rather than separating them out into different areas of the page.

Here's a hastily pasted together example of what I mean (using my uber-design-skilz) Note the west-zone and kuma-demo-ns underneath the name of the service.

Screenshot 2024-09-19 at 15 22 36

This not only displays the information, but also in putting all these things together helps to explain that all of these 3 properties are related and used for "naming the thing".


Note: I've dropped the words/labels "Namespace" and "Zone" and just displayed the values (west-zone / kuma-demo-ns), but we could also use a small icon+tooltip in-front of the value to indicate exactly what it is. If we used the same icons everywhere for the same things, users would quickly learn what each icon means without having to activate a tooltip.

@johncowen johncowen added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Sep 19, 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 Sep 23, 2024
@johncowen johncowen added this to the backlog milestone Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Development

No branches or pull requests

2 participants