default behavior of kube_config.load_kube_config() doesn't respect KUBECONFIG env var

[kattmang]

For setups where you have multiple kube config files, kubectl respects the KUBECONFIG env variable which allows for appending multiple kube config file locations.

I believe that

python/kubernetes/config/kube_config.py

Line 292 in ce8e082

if config_file is None:

should look at the environment's KUBECONFIG if it exists and load in all kube configs from there. If it doesn't exist, then use KUBE_CONFIG_DEFAULT_LOCATION.

[tomplus]

This feature has to be added to python-base repo, ref issue: kubernetes-client/python-base#62

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.