Skip to content
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.

ks init fails when using $KUBECONFIG env var #251

Closed
lblackstone opened this issue Dec 22, 2017 · 1 comment
Closed

ks init fails when using $KUBECONFIG env var #251

lblackstone opened this issue Dec 22, 2017 · 1 comment

Comments

@lblackstone
Copy link
Contributor

lblackstone commented Dec 22, 2017

I'm getting the following error when trying to run ks init ks-example:

ERROR No current context found. Make sure a kubeconfig file is present

My cluster's kubeconfig is referenced in the KUBECONFIG env var, and I can interact with the cluster via kubectl.

This appears to be a regression introduced in d252456

Here is the kubeconfig I'm using:

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: <redacted>
    server: https://<redacted>:443
  name: levi
contexts:
- context:
    cluster: levi
    user: kubelet
  name: ""
current-context: ""
kind: Config
preferences: {}
users:
- name: kubelet
  user:
    client-certificate-data: <redacted
    client-key-data: <redacted
@lblackstone
Copy link
Contributor Author

After further investigation, looks like this is related to coreos/tectonic-installer#1906

The kubeconfig doesn't have a named context or active context set.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant