kubernetes/pkg/controller/certificates
Monis Khan cd91e59f7c
csr: add expirationSeconds field to control cert lifetime
This change updates the CSR API to add a new, optional field called
expirationSeconds.  This field is a request to the signer for the
maximum duration the client wishes the cert to have.  The signer is
free to ignore this request based on its own internal policy.  The
signers built-in to KCM will honor this field if it is not set to a
value greater than --cluster-signing-duration.  The minimum allowed
value for this field is 600 seconds (ten minutes).

This change will help enforce safer durations for certificates in
the Kube ecosystem and will help related projects such as
cert-manager with their migration to the Kube CSR API.

Future enhancements may update the Kubelet to take advantage of this
field when it is configured in a way that can tolerate shorter
certificate lifespans with regular rotation.

Signed-off-by: Monis Khan <mok@vmware.com>
2021-07-01 23:38:15 -04:00
..
approver Update auth OWNERS files to only use aliases 2021-04-07 10:46:03 -04:00
authority csr: correctly handle backdating of short lived certs 2021-06-23 15:36:11 -04:00
cleaner hack/update-bazel.sh 2021-02-28 15:17:29 -08:00
rootcacertpublisher include description of what kube-root-ca.crt can be used to verify 2021-04-08 10:43:41 -04:00
signer csr: add expirationSeconds field to control cert lifetime 2021-07-01 23:38:15 -04:00
certificate_controller_test.go Switch CSR approver/signer/cleaner controllers to v1 2020-06-05 18:45:34 -04:00
certificate_controller_utils_test.go Switch CSR approver/signer/cleaner controllers to v1 2020-06-05 18:45:34 -04:00
certificate_controller_utils.go Some comments' typos 2020-11-02 15:05:23 +08:00
certificate_controller.go [pkg/controller/certificates]: remove staled func comments 2020-07-11 17:08:28 +08:00
OWNERS Merge pull request #72525 from justinsb/owners_should_not_be_executable 2019-02-14 23:55:45 -08:00