Add an option to flux-cli to use the namespace declared in the kubeconfig context #2768
-
|
Hi, It will be great to add an option to flux-cli to use the namespace declared in the kubeconfig context This will allow us, when we work on specific namespace, to use both kubectl and flux without specifying -n. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Right now we allow changing the default namespace from export FLUX_SYSTEM_NAMESPACE=my-namespaceWe could introduce a new env var that would make the CLI read the namespace from the kubeconfig current context e.g.: export FLUX_SYSTEM_NAMESPACE_FROM_CONTEXT=true |
Beta Was this translation helpful? Give feedback.
-
|
I think a new knob to make the CLI take the context into account would not really improve the situation. Putting the difficulties around upgrade paths and backwards compatibility aside for a minute. I think the best option in terms of UX would be to default to This would make tools like |
Beta Was this translation helpful? Give feedback.
-
|
Suggestion implemented in #5297 |
Beta Was this translation helpful? Give feedback.
Right now we allow changing the default namespace from
flux-systemto something else with:export FLUX_SYSTEM_NAMESPACE=my-namespaceWe could introduce a new env var that would make the CLI read the namespace from the kubeconfig current context e.g.:
export FLUX_SYSTEM_NAMESPACE_FROM_CONTEXT=true