Cluster/context selection and multi-file KUBECONFIG about kube-no-trouble HOT 6 CLOSED

@stepanstipl Can confirm it works. Thanks!

from kube-no-trouble.

Hi @thomas-riccardi, thanks for opening this issue. I assume the "cross-file" context selection is something that works out of the box with kubectl, correct? I will have to check how that is implemented, but the idea is to behave in the same way, so it sounds like something we can look into.

Context selection makes sense. I think kubectl supports this via --context, but also --cluster and --user, flags. So probably something we can add (or at least context for a start).

from kube-no-trouble.

Hi @stepanstipl

I assume the "cross-file" context selection is something that works out of the box with kubectl, correct?

Yes; that's indeed a little bit surprising for k8s tools developers but it works transparently on kubectl.
It probably merges all yaml files into one config object (concat all arrays (clusters, contexts, users) (with dedup? error on conflict?) except current-context, which seems to be taken from the first file), then work from that as usual.
kubectl config view shows the parsed/merged config.

Context selection makes sense. I think kubectl supports this via --context, but also --cluster and --user, flags. So probably something we can add (or at least context for a start).

Personally I only use --context as --cluster probably also requires --user: slower to type. So starting with --context would be perfect for me :), and hopefully not just me.

from kube-no-trouble.

Just stumbled across this tool as something to investigate, but we also have the same issue; multiple kubeconfig files.

from kube-no-trouble.

@thomas-riccardi @ryan-dyer-sp Support for both multiple kubeconfig files and selecting context has now been added and is part of the latest 0.5.0 release. Please give it a go and let me know if there are any issues. Cheers 👍

from kube-no-trouble.

@stepanstipl I confirm this works in our setup, great with kubectx and explicit --context option, thx!

(though 0.5.0 broke --additional-kind: #204)

from kube-no-trouble.