Description
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.