-
Notifications
You must be signed in to change notification settings - Fork 4k
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
VPA: Remove TLS client cert lookup logic #1692
VPA: Remove TLS client cert lookup logic #1692
Conversation
cc: @schylek |
Doesn't compile. Please fix. |
Actual verification is already turned off in the code and appears to be just a no-op. Moreover, VPA Admission Controller (acting as TLS Server) does not request client (apiserver, acting as TLS Client) to present certificate. This code is fragile, depends on apiserver having requestheader-client-ca-file certificate generated and supplied, and most importantly does not add any security or any other value.
@mwielgus, thanks, cleaned up unused imports. |
@tkulczynski - I believe you are the one who implemented this. Could you please take a look at the PR? Is this code needed? |
cc: @jbartosik |
I'll take a look later today. |
/lgtm |
Thanks @jbartosik! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bskiba The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Actual verification was turned off from the initial commit and is still not enabled, so the whole construct does not add value.
Also depending on
requestheader-client-ca-file
by itself renders VPA incompatible with apiserver installations which does not use such certificate with VPA Admission Controller crash-looping with:vpa-admission-controller-X-Y:admission-controller F0214 18:15:09.448204 9 config.go:60] cannot find the ca.crt in the configmap, configMap.Data is map[string]string{"client-ca-file":"...skipped..."}
In addition to the above it worth noting that
requestheader-client-ca-file
appears to be just a wrong place to look for possible apiserver client certificate (I don't think there is any).