kube2sky ignores insecure-skip-verify in kubeconfig

[aaronlevy]

Trying to set insecure-skip-verify:true in a kubeconfig for use by kube2sky. However, the setting seems to be ignored (API requests fail with "certificate signed by unknown authority").

However, if a server is also specified in the kubeconfig, the insecure-skip-verify flag will be respected, and kube2sky can communicate with apiserver.

[thockin]

@JeffML @mikedanese - what is expected behavior here?

On Mon, Aug 31, 2015 at 3:45 PM, Aaron Levy notifications@github.com
wrote:

Trying to set insecure-skip-verify:true in a kubeconfig for use by
kube2sky. However, the setting seems to be ignored (API requests fail with
"certificate signed by unknown authority").

However, if a server is also specified in the kubeconfig, the
insecure-skip-verify flag will be respected, and kube2sky can communicate
with apiserver.

—
Reply to this email directly or view it on GitHub
#13411.

[lavalamp]

I think what is happening is that putting the server location in the kubeconfig file makes it not ignore the file.

[thockin]

Is that "correct"?
On Sep 1, 2015 11:28 AM, "Daniel Smith" notifications@github.com wrote:

I think what is happening is that putting the server location in the
kubeconfig file makes it not ignore the file.

—
Reply to this email directly or view it on GitHub
#13411 (comment)
.

[aaronlevy]

Closing this as it's a year old, and I was probably being lazy at the time by not generating proper certs.