Mention time range where kubelet might renew cert
The docs don't mention when the kubelet will attempt to renew a cert, which causes concern when one notices that certain certificates are being renewed and others are not. Adding the time frame adds certainty, so that if an user notices a kubelet cert expiring in less than 30d, they know something is misconfigured and should be looked at.
This commit is contained in:
@@ -69,8 +69,9 @@ write that to disk, in the location specified by `--cert-dir`. Then the kubelet
|
|||||||
will use the new certificate to connect to the Kubernetes API.
|
will use the new certificate to connect to the Kubernetes API.
|
||||||
|
|
||||||
As the expiration of the signed certificate approaches, the kubelet will
|
As the expiration of the signed certificate approaches, the kubelet will
|
||||||
automatically issue a new certificate signing request, using the Kubernetes
|
automatically issue a new certificate signing request, using the Kubernetes API.
|
||||||
API. Again, the controller manager will automatically approve the certificate
|
This can happen at any point between 30% and 10% of the time remaining on the
|
||||||
|
certificate. Again, the controller manager will automatically approve the certificate
|
||||||
request and attach a signed certificate to the certificate signing request. The
|
request and attach a signed certificate to the certificate signing request. The
|
||||||
kubelet will retrieve the new signed certificate from the Kubernetes API and
|
kubelet will retrieve the new signed certificate from the Kubernetes API and
|
||||||
write that to disk. Then it will update the connections it has to the
|
write that to disk. Then it will update the connections it has to the
|
||||||
|
|||||||
Reference in New Issue
Block a user