Skip to content

Commit 12c57e6

Browse files
authored
Merge pull request #28347 from Shubham82/fix-Certificate_Rotation_for_the_kubelet
Correct the Configure Certificate Rotation for the Kubelet docs.
2 parents 64a7157 + deba580 commit 12c57e6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/en/docs/tasks/tls/certificate-rotation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,8 @@ The kubelet uses certificates for authenticating to the Kubernetes API. By
2727
default, these certificates are issued with one year expiration so that they do
2828
not need to be renewed too frequently.
2929

30-
Kubernetes 1.8 contains [kubelet certificate
31-
rotation](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/), a beta feature
30+
Kubernetes contains [kubelet certificate
31+
rotation](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/),
3232
that will automatically generate a new key and request a new certificate from
3333
the Kubernetes API as the current certificate approaches expiration. Once the
3434
new certificate is available, it will be used for authenticating connections to
@@ -62,7 +62,7 @@ criteria, it will be auto approved by the controller manager, then it will have
6262
a status of `Approved`. Next, the controller manager will sign a certificate,
6363
issued for the duration specified by the
6464
`--cluster-signing-duration` parameter, and the signed certificate
65-
will be attached to the certificate signing requests.
65+
will be attached to the certificate signing request.
6666

6767
The kubelet will retrieve the signed certificate from the Kubernetes API and
6868
write that to disk, in the location specified by `--cert-dir`. Then the kubelet

0 commit comments

Comments
 (0)