HOSTEDCP-1256: control-plane-pki-operator: add an operator for managing PKI - #3193
Conversation
|
@stevekuznetsov: This pull request references HOSTEDCP-1256 which is a valid jira issue. DetailsIn response to this:
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. |
| certrotation.RotatedSigningCASecret{ | ||
| Namespace: hostedControlPlane.Namespace, | ||
| Name: manifests.CustomerSystemAdminSigner(hostedControlPlane.Namespace).Name, | ||
| Validity: 7 * rotationDay, |
There was a problem hiding this comment.
In my mind, I was thinking in the neighborhood of 1d validity and 12h rotation.
However, as long as we can adjust later, I'm not inclined to hold up the PR for consensus on this as long as we use something reasonable.
a3fbeca to
43479e6
Compare
|
Added management of the new PKI controller to |
43479e6 to
4778112
Compare
87840de to
eac9b6e
Compare
✅ Deploy Preview for hypershift-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Nice, thanks! please let's make sure before merging we reuse existing e2e test for the new validation, squash commits and document in the PR desc and the operator code what it does concretely e.g. "Combines a CustomerSystemAdminSignerCA within the TotalKASClientCABundle and ensures creation and rotation of a signer and client certs that can be used to create a break glass kubeconfig"? |
374ffee to
45c905b
Compare
45c905b to
cddfe64
Compare
|
/retest |
|
/test e2e-aws |
cddfe64 to
c6db6df
Compare
|
/test e2e-ibmcloud-roks |
2d50de6 to
ffcc993
Compare
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
e858504 to
a594f1b
Compare
In the future, we'd like to lean on the library-go approach for PKI management to gain access to some of the features it provides as well as increasing the number of engineers who are able to maintain PKI in HyperShift as we'd no longer be using an in-house solution. The first step in this process is adding a new controller to manage PKI for the hosted control planes, and having it manage: - a new signer for customers' break-glass credentials - a trust bundle of active signers - a client certificate and key signed by the currently-valid signer - a total client CA bundle (which is, for now, the smae as 2) The control-plane-operator consumes the total client CA and aggregates it into the current KAS client CA flow. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
a594f1b to
13094ab
Compare
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
fb18245 to
0c53faa
Compare
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
0c53faa to
9d6c02a
Compare
|
/test all |
|
/lgtm |
|
/retest-required |
1 similar comment
|
/retest-required |
go.mod: update vendors
Signed-off-by: Steve Kuznetsov skuznets@redhat.com
*: add a control-plane-pki-operator
In the future, we'd like to lean on the library-go approach for PKI
management to gain access to some of the features it provides as well as
increasing the number of engineers who are able to maintain PKI in
HyperShift as we'd no longer be using an in-house solution.
The first step in this process is adding a new controller to manage PKI
for the hosted control planes, and having it manage:
The control-plane-operator consumes the total client CA and aggregates
it into the current KAS client CA flow.
Signed-off-by: Steve Kuznetsov skuznets@redhat.com
/assign @sjenning @deads2k