-
Notifications
You must be signed in to change notification settings - Fork 189
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
API-1438: Split the global trust with kube-control-plane client certs #870
API-1438: Split the global trust with kube-control-plane client certs #870
Conversation
94e3cee
to
48e47c5
Compare
/kind cleanup |
48e47c5
to
3aabaf1
Compare
Linking to USHIFT-278 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of questions. Otherwise, it looks good to me.
In order to understand this PR, it's good to have the following link as reference:
and this is just the first change to a better alignment with OpenShift's certificate management.
Let's start splitting away the global trust from the root CA: - generate a kube-control-plane-signer - have it generate client certs for KCM and kube-scheduler - create a CA bundle only for the client CA certs Currently, the client CAs bundle contains the new signer plus the root CA since we're going to be chipping away the client certs one by one.
The GetRootCA() function allowed retrieval of the util-module internal rootCA variable and it could've been therefore easily modified by anyone.
3aabaf1
to
07f3636
Compare
07f3636
to
b0fc30d
Compare
Fatal!
|
b0fc30d
to
d109a47
Compare
@stlaz: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: oglok, stlaz 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 |
This PR attempts to split away the client certs for kube-scheduler and KCM from the global trust provided by the root CA.