-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Have "All" as default namespace instead of "default" #10871
Comments
From #11233: We're in the process of rolling out namespace usage within our infrastructure. Engineers will use the Nomad UI to inspect the state of the world, but their resources may not be in the default namespace - or will be confused with one that does exist in that namespace - and as such they may be confused and interact with the wrong resource. We already had this issue while working on the functionality with our deploy system. We deployed a nomad job to a new namespace but forgot to switch namespaces in the sidebar, so we couldn't find the job. This also impacted the local cli, but I think that can be done as a separate ticket. |
@josegonzalez would it be possible to list the pages where you are looking for this? In #11233 you mentioned job/storage, but I think only a few of our list endpoints support the |
@lgfa29 both those pages are where I’m currently looking. |
Looking at the UI code in more details, I noticed that the |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Proposal
When there are multiple namespaces, the UI is defaulting to "default" option. It would be great if it defaults to the "All" option.
If this is a resource intensive task, may be we can fall back to default if the number of jobs or namespaces crosses a threshold? May be a configurable setting may be?
Use-cases
In my case, I have 4 namespaces and would like to see all jobs instead of "default" namespace where I have only house-keeping jobs.
Attempted Solutions
None
The text was updated successfully, but these errors were encountered: