Support for / ignore comma separated KUBECONFIG env paths about kubeswitch

[alexdyas]

Hi, sorry I missed this being closed. Just tried it, works perfectly, thanks!

[danielfoehrKn]

Am I doing something wrong?

No, it is just not supported yet. But it does not sound very complicated.
I'll try to add it, but cannot give you a concrete timeline :)

[alexdyas]

I'm a bit confused in that case. For kubectl to work with multiple kubeconfig files I have to set the KUBECONFIG environment variable using the colon separated list of config files, otherwise it doesn't see any config. However for kubeswitch to work I have to unset the KUBECONFIG variable, and instead set the wildcard in switch-config.yaml. I don't understand how both kubectl and kubeswitch could both work if I want multiple config files.

[danielfoehrKn]

Currently kubeswitch does not work with multiple paths in the KUBECONFIG. It will always try to load whatever is configured in the environment variable and throws an error.

As soon as kubeswitch supports it the flow will look like this:

• KUBECONFIG env variable has multiple paths
• kubeswitch displays contexts from multiple paths + what is configured in the switch-config.yaml
• User selects a context
• kubeswitch creates a temporary kubeconfig file containing only your selected context.
• the KUBECONFIG env variable is updated to point to the temporary kubeconfig.
• kubectl works against one context in one kubeconfig file. If you want to switch contexts, you need to use switch again. You need to have both the kubeconfig files in the switch-config.yaml, otherwise you cannot select them as they are not in the KUBECONFIG env variable any more.

As an alternative: Do not set multiple paths in the KUBECONFIG env variable. Set multiple paths in the switch.config file like shown in the docs.

Does that help?

[alexdyas]

Yes that makes sense I think. Thanks for the feedback.

[danielfoehrKn]

I created this commit included in the release 0.4.8 so you can try it out.

If it does not work for you, feel free to open the issue again.