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

InsecureSkipTLSVerify not implemented #55

Closed
sidmutha opened this issue Jul 20, 2017 · 2 comments
Closed

InsecureSkipTLSVerify not implemented #55

sidmutha opened this issue Jul 20, 2017 · 2 comments

Comments

@sidmutha
Copy link
Contributor

In the config being passed to k8s.NewClient, I set the flag InsecureSkipTLSVerify to truefor a particular cluster. But any request made to this cluster using the client returned by k8s.NewClient gives x509: certificate signed by unknown authority. I guess this is happening because the flag is not being respected in the library. I went through the source code and confirmed the same. Any help?

@ericchiang
Copy link
Owner

Yeah it looks like I overlooked this option. As a work around you should probably provide the CA.

Feel free to provide a PR to make this option respected.

@ericchiang
Copy link
Owner

closed via #56

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

2 participants