Not recognized multiple kube-config files in KUBECONFIG env variable about helm-2to3 HOT 10 CLOSED

it needs to be implemented :)

for now use export KUBECONFIG=single_kubeconfig_file

from helm-2to3.

@alexandrsemak It probably needs to handle different kubeconfigs instead of using the standard/default. However, the error message is rather confusing. Just trying to get better understanding of your set-up so I can troubleshoot this.

For the case that is working, how are you using one kubeconfig file wrt:

• Helm 2
• Helm 3
• plugin

For the case that is not working, how are you using multiple kubeconfig files wrt:

• Helm 2
• Helm 3
• plugin

from helm-2to3.

@hickeyma
With multiple kubeconfig i have KUBECONFIG=$cluster1:/$cluster2:.... and kubectx for switching between them.
With single kubeconfig file I have used the same evn but just left only one kubeconfig KUBECONFIG=$cluster1

from helm-2to3.

@alexandrsemak Does Helm v2 and Hem v3 have any issues with the multiple kubeconfigs? Do you have to pass --kubeconfig for running Helm commands?

from helm-2to3.

@hickeyma
with kubectx i don't use --kubeconfig
kubectx use kubectl config set-context under the hood

from helm-2to3.

I was able to reproduce it with export KUBECONFIG=$cluster1:/$cluster2 got the same
error:

$ helm3 2to3 convert --tiller-out-cluster --dry-run mysql
NOTE: This is in dry-run mode, the following actions will not be executed.
Run without --dry-run to take the actions described below:

Release "mysql" will be converted from Helm 2 to Helm 3.
[Helm 3] Release "mysql" will be created.
2019/09/25 10:26:55 stat /Users/rimas/.kube/test-cluster-1_config:/Users/rimas/.kube/test-cluster-2_config: no such file or directory
Error: plugin "2to3" exited with error

2to3 plugin treats them as one file.

from helm-2to3.

ideally it should not be part of the plugin, we could just add a note, single kubeconfig is only supported.

this plugin is only for releases migration purposes, no needs to support export KUBECONFIG=$cluster1:/$cluster2 use case.

from helm-2to3.

why plugin just not able use current context? which use kubectl with set-context

from helm-2to3.

How to use single kubeconfig in env var KUBECONFIG was documented in #63

from helm-2to3.

Finally, getting back to this issue again.

I have tracked it down to an issue with the helm-plugin-utils library. Issue was already raised in project and have pushed a PR to fix it

from helm-2to3.