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

Do not require kubectl proxy: allow reading kubeconfig file #95

Closed
hjacobs opened this issue Jan 15, 2017 · 1 comment
Closed

Do not require kubectl proxy: allow reading kubeconfig file #95

hjacobs opened this issue Jan 15, 2017 · 1 comment
Milestone

Comments

@hjacobs
Copy link
Owner

hjacobs commented Jan 15, 2017

Try to read ~/.kube/config by default and use it to directly connect to the default context thus not requiring kubectl proxy anymore.

Also add --kubeconfig-path option to read arbitrary kubeconfig file containing credentials (possibly client certs #72).

@hjacobs hjacobs self-assigned this Jan 15, 2017
@hjacobs hjacobs changed the title Do not require kubectl proxy Do not require kubectl proxy: allow reading kubeconfig file Jan 15, 2017
@hjacobs hjacobs added this to the 1.0 milestone Jan 15, 2017
hjacobs added a commit that referenced this issue Jan 15, 2017
@hjacobs
Copy link
Owner Author

hjacobs commented Jan 15, 2017

Actually reading ~/.kube/config by default is impossible from within a Docker container (as user would need to mount it), so I'll keep the http://localhost:8001 proxy URL as default (this only requires passing --net=host to docker run).

hjacobs added a commit that referenced this issue Jan 15, 2017
@hjacobs hjacobs removed their assignment Jan 15, 2017
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