support/warn if KUBECONFIG has multiple paths

[maxandersen]

Describe the bug
when having KUBECONFIG like:

echo $KUBECONFIG
/Users/max/.kube/config:/Users/max/.kube/kubeconfig:/Users/max/Downloads/openshift-install-mac-4.2.2/myinstall/auth/kubeconfig

kubernetes client related operations fails siliently and you get "Unknown host kubernetes.default.svc: nodename nor servname provided, or not known"

Expected behavior
read the working KUBECONFIG or at least warn.

Actual behavior

[geoand]

@iocanel are there any utilities in the Kubernetes Client that deal with this or should we just roll something up in Quarkus?

[iocanel]

No, this is a limitation of the client and needs to be fixed there I am afraid.

[geoand]

Are you going to take care of it, or should we engadge the DevTools folks?

[iocanel]

Let's ask Rohan or Marc if the can take care of it.

[geoand]

@rohanKanojia can you take a look please?

[rohanKanojia]

We will take care of it. Thanks for letting us know

[geoand]

Great, thanks

[manusa]

What would the preferred behavior be?

As of now I see a couple of corner cases to "read the working KUBECONFIG":

• More than one configuration works
• None works

Maybe pick the first one and show a WARNING like "Detected several configurations in KUBECONFIG environment variable, using ${firstConfiguration}"

[geoand]

Maybe pick the first one and show a WARNING like "Detected several configurations in KUBECONFIG environment variable, using ${firstConfiguration}"

I think that is a reasonable way to move forward. Also perhaps a message on how users can get rid of the multiple configurations would be nice.

[manusa]

We just released https://github.com/fabric8io/kubernetes-client/releases/tag/v4.10.0

Warning should be visible in this new version.

[geoand]

Excellent!

[geoand]

Closing as the client already addressed this issue