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

Allow to set the namespace in which to apply resources from the UI #2925

Open
joaquimrocha opened this issue Feb 19, 2025 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@joaquimrocha
Copy link
Collaborator

Is your feature request related to a problem? Please describe the impact that the lack of the feature requested is creating.

We allow to apply resources from the UI using the Create button from within the cluster view. It would be nice if we could specify which namespace to set the new resources in. This would affect only resources that don't have a namespace set (which will pick the default one in this case), so this can be seen as overriding the default namespace.

Describe the solution you'd like

There should be a Default Namespace: [ my-namespace ] picker (with autocomplete) in the create dialog.
This autocomplete points to the currently set default namespace for the current cluster. If none is specified, try to use one called default, if no default is set and no default namespace exists, just do not use this feature and show a warning icon next to it which on hover tells the user that there's no default branch.

If the user writes a namespace that doesn't exist, we should just an info icon which on hover tells the user that this namespace will be created. In this case, the namespace is created before applying the resources.

What users will benefit from this feature?

Every one willing to apply new resources but forgot to create a new namespace. Or are used to the -n option of kubectl when applying.

Additional context

Design to be added later.

@adwait-godbole
Copy link
Contributor

@joaquimrocha what should be the behavior if the user specifies a namespace in the YAML manifest itself? that should take precedence over this feature right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

2 participants