-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Plumbing for dynamic apiserver serving certificates #83580
Plumbing for dynamic apiserver serving certificates #83580
Conversation
Hi @jackkleeman. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/assign @deads2k |
5dac194
to
010d2ba
Compare
staging/src/k8s.io/apiserver/pkg/server/dynamiccertificates/static_content.go
Outdated
Show resolved
Hide resolved
staging/src/k8s.io/apiserver/pkg/server/dynamiccertificates/cert_key.go
Outdated
Show resolved
Hide resolved
staging/src/k8s.io/apiserver/pkg/server/dynamiccertificates/tlsconfig.go
Show resolved
Hide resolved
e0b3bda
to
94e03bc
Compare
94e03bc
to
d450391
Compare
staging/src/k8s.io/apiserver/pkg/server/dynamiccertificates/client_ca.go
Show resolved
Hide resolved
return fmt.Errorf("invalid serving cert keypair: %v", err) | ||
} | ||
|
||
// error is not possible given above call to X509KeyPair |
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.
check anyway please because I don't trust it.
/ok-to-test minor comments only. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, jackkleeman 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 |
d450391
to
02d128d
Compare
/lgtm |
We create and use a dynamic certificate provider for the main apiserver serving certificates: SNI will be handled separately later. Currently we only use static serving certificate providers, so the files are not reloaded, but we should be able to move to a provider that is able to reload later on.
02d128d
to
6f89f10
Compare
just a comment change /lgtm |
/test pull-kubernetes-e2e-gce-device-plugin-gpu |
/retest |
/test pull-kubernetes-integration |
/test pull-kubernetes-e2e-gce |
Hi @jackkleeman and @deads2k , is it possible to just take this PR and have a cherry -pick to other k8s versions like 1.16 and 1.15 ? What are the other changes or architecture we need to care about for this change to get merge in other k8s versions. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR is initial plumbing towards allowing apiserver default (non-SNI) serving certificates to be reloaded from disk. We change the Cert field in the
SecureServingInfo
to be aDynamicCertKeyContentProvider
, which currently is implemented by a static provider that doesn't re-read off of disk, but this can change in a subsequent PR which will add a dynamic provider.Does this PR introduce a user-facing change?: