Skip to content

Commit be58015

Browse files
authored
Merge pull request #57969 from ShaunaDiaz/OSDOCS-5651
OSDOCS-5651: update cert rotation images for TP
2 parents bba39db + 94356c3 commit be58015

File tree

4 files changed

+27
-32
lines changed

4 files changed

+27
-32
lines changed
46.4 KB
Loading
45.8 KB
Loading

microshift_troubleshooting/microshift-troubleshooting.adoc

Lines changed: 0 additions & 16 deletions
This file was deleted.

modules/microshift-certificate-lifetime.adoc

Lines changed: 27 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -11,30 +11,41 @@
1111
. Short-lived certificates having certificate validity of one year.
1212
. Long-lived certificates having certificate validity of 10 years.
1313

14-
Most server or leaf certificates are short-lived.
14+
Most server or leaf certificates are short-term.
1515

1616
An example of a long-lived certificate is the client certificate for `system:admin user` authentication, or the certificate of the signer of the `kube-apiserver` external serving certificate.
1717

1818
[id="microshift-certificate-rotation_{context}"]
1919
== Certificate rotation
20-
As certificates age, {product-title} can be restarted to rotate certificates. A certificate that is close to expiring might also automatically cause a restart. Read the following situation overviews to understand the actions at each moment in time:
21-
22-
. Green zone:
23-
.. When a short-term certificate is 5 months old, no rotation occurs.
24-
.. When a long-term certificate is 8.5 years old, no rotation occurs.
25-
26-
. Yellow zone:
27-
.. When a short-term certificate is 8 months old, it is rotated when {product-title} starts or restarts.
28-
.. When a long-term certificate is 9 years old, it is rotated when {product-title} starts or restarts.
29-
30-
. Red zone
31-
.. When a short-term certificate is 8 months old, {product-title} restarts to rotate and apply a new certificate.
32-
.. When a long-term certificate is 9 years old, {product-title} restarts to rotate and apply a new certificate.
20+
Certificates that are expired or close to their expiration dates need to be rotated to ensure continued {product-title} operation. When {product-title} restarts for any reason, certificates that are close to expiring are rotated. A certificate that is set to expire imminently, or has expired, can cause an automatic {product-title} restart to perform a rotation.
3321

3422
[NOTE]
3523
====
3624
If the rotated certificate is a Certificate Authority, all of the certificates it signed rotate.
3725
====
3826

39-
.Stoplight timeline of {product-title} certificate validity.
40-
image::microshift-cert-rotation.png[<{product-title} graph with symbolic green-yellow-red stoplight map of certificates>]
27+
[id="microshift-st-certificate-rotation_{context}"]
28+
=== Short-term certificates
29+
The following situations describe {product-title} actions during short-term certificate lifetimes:
30+
31+
. No rotation:
32+
.. When a short-term certificate is up to 5 months old, no rotation occurs.
33+
34+
. Rotation at restart:
35+
.. When a short-term certificate is 5 to 8 months old, it is rotated when {product-title} starts or restarts.
36+
37+
. Automatic restart for rotation:
38+
.. When a short-term certificate is more than 8 months old, {product-title} can automatically restart to rotate and apply a new certificate.
39+
40+
[id="microshift-lt-certificate-rotation_{context}"]
41+
=== Long-term certificates
42+
The following situations describe {product-title} actions during long-term certificate lifetimes:
43+
44+
. No rotation:
45+
.. When a long-term certificate is up to 8.5 years old, no rotation occurs.
46+
47+
. Rotation at restart:
48+
.. When a long-term certificate is 8.5 to 9 years old, it is rotated when {product-title} starts or restarts.
49+
50+
. Automatic restart for rotation:
51+
.. When a long-term certificate is more than 9 years old, {product-title} can automatically restart to rotate and apply a new certificate.

0 commit comments

Comments
 (0)