Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixed issues related to TLS verification. #8

Closed

Conversation

JohnCMcDonough
Copy link

I found two issues related to TLS verification.

Originally, the check relied on "falsy" conversions that were invalid.

elt.cluster['insecure-skip-tls-verify'] == 'true'

where elt.cluster['insecure-skip-tls-verify'] was a boolean, and 'true' was a string.

true == 'true' is false.

The other issue, is that it expected certificate-authority-data and certificate-authority even if skipTLSVerify was true.

@brendandburns
Copy link
Contributor

@JohnCMcDonough LGTM. Please sign the CLA and then we can merge this!

@JohnCMcDonough
Copy link
Author

JohnCMcDonough commented Feb 9, 2018

Alright, I've signed the agreement! At least, I think I have...

@brendandburns
Copy link
Contributor

CLA still shows as missing, is your email associated with your github the same as what you signed from?

@brendandburns
Copy link
Contributor

(also now needs a rebase...)

@esselius
Copy link

esselius commented Apr 27, 2018

Is this CLA being taken care of?

My workaround was making the kube config key value be a string, but then kubectl complains and I have to switch it back and forth..

@brendandburns
Copy link
Contributor

This PR is now obsolete, since the requirement for CA cert was removed.

Closing.

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

Successfully merging this pull request may close these issues.

3 participants