cli not able to parse multi segment `$KUBECONFIG`

[k15r]

Description

kubectl works fine with a $KUBECONFIG set to something like this:

/Users/foo/kubeconfig1:/Users/foo/kubeconfig2:/Users/foo/kubeconfig3

internally all mentioned kubeconfig files will be merged into a single kubeconfig and then parsed as one.

This allow overriding the eg current-context without modifying one of the files, by just adding another empty kubeconfig to the start of the list.

in kyma using such a $KUBECONFIG results in the following error:

 WARN    service/runner.go:45    Runner: failing reconciliation of 'CRDs' in version '2.0.4' with profile 'evaluation': yaml: line 2: mapping values are not allowed in this context

This error message is absolutely useless, as it does not specify which yaml file is faulty. It does not even point you in the direction of the kubeconfig.

Expected result

• either support such multi segment $KUBECONFIG (preferred solution, as you can use the same for kubectl and for kyma)
• or at least print a usable error message

[kyma-stale-bot[bot]]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

[kyma-stale-bot[bot]]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

[kyma-stale-bot[bot]]

This issue has been automatically closed due to the lack of recent activity. /lifecycle rotten