Skip to content
This repository has been archived by the owner on Jan 19, 2023. It is now read-only.

Configuration is not loaded properly #150

Closed
MOZGIII opened this issue Aug 10, 2019 · 3 comments · Fixed by #403
Closed

Configuration is not loaded properly #150

MOZGIII opened this issue Aug 10, 2019 · 3 comments · Fixed by #403
Assignees
Labels
api bug Something isn't working

Comments

@MOZGIII
Copy link

MOZGIII commented Aug 10, 2019

I got this error:

failed to init cluster client: invalid configuration: [context was not found for specified context: c1-admin@c1, cluster has no server defined]

Context for my c1 cluster is defined at a separate file, and it's referenced via KUBECONFIG:

$ echo $KUBECONFIG 
/home/me/.kube/config:/home/me/.kube/config.d/c1

kubectl wotks properly with this setup.

@wwitzel3 wwitzel3 added api bug Something isn't working labels Aug 12, 2019
@bryanl
Copy link
Contributor

bryanl commented Aug 15, 2019

This issue has been resolved in #164. Please reopen if this is not the case.

@bryanl bryanl closed this as completed Aug 15, 2019
@peterrosell
Copy link

This worked in version 0.6.0-0.8.0, but not anymore. Tested in version 0.9.0 and 0.9.1. I'm running on Ubuntu 18.04 and have two files specified via the environment variable KUBECONFIG.

@wwitzel3
Copy link
Contributor

wwitzel3 commented Nov 5, 2019

Fixed in master, will be apart of the nightly build tomorrow.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants