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

Add status/state in a position hierarchically above tabs #3242

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

Add status/state in a position hierarchically above tabs #3242

johncowen 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

@johncowen
Copy link
Contributor

Description

We decided that it would be good to be able to see the status/state of a resource no matter what tab you might be on when on its page.

For example, if I'm on an XDS Configuration tab for a dataplane and I'm refreshing the page for whatever reason, I would still like to notice if the dataplane itself suddenly drops or becomes unhealthy.

If we put the state in the same general area as the title (which is always visible), then this means the state of the resource is always visible no matter what sub-details I'm looking at. Moreover the UI badges that we use for state are relatively small and self-explanatory so they take up very little space if used on their own (or even sometimes with tooltipping)

The above example details the usecase for Dataplanes but there are probably other resources that use a badge to show some sort of uber-important state (e.g. Zones), we should do the same in these cases so we remain consistent.

There is already some design options/suggestions for this 👀

@johncowen johncowen added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Dec 2, 2024
@bartsmykla bartsmykla 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 Dec 2, 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