|
1 | 1 | // Module included in the following assemblies: |
2 | 2 | // |
3 | | -// * microshift/microshift-things-to-know.adoc |
| 3 | +// * microshift_troubleshooting/microshift-responsive-restarts-cas.adoc |
4 | 4 |
|
5 | 5 | :_mod-docs-content-type: CONCEPT |
6 | 6 | [id="microshift-certificate-lifetime_{context}"] |
7 | 7 | = Security certificate lifetime |
8 | 8 |
|
9 | | -{microshift-short} certificates are separated into two basic groups: |
| 9 | +[role="_abstract"] |
| 10 | +{microshift-short} certificates are digital certificates that secure communication with communication protocols such as HTTPS. They fall into two basic categories: |
10 | 11 |
|
11 | | -. Short-lived certificates having certificate validity of one year. |
12 | | -. Long-lived certificates having certificate validity of 10 years. |
| 12 | +Short-lived certificates:: Have a certificate validity of one year. Most server or leaf certificates are short-lived. |
| 13 | +Long-lived certificates:: Have a certificate validity of 10 years. 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. |
13 | 14 |
|
14 | | -Most server or leaf certificates are short-lived. |
15 | | - |
16 | | -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. |
17 | | - |
18 | | -[id="microshift-certificate-rotation_{context}"] |
19 | | -== Certificate rotation |
20 | | -Certificates that are expired or close to their expiration dates need to be rotated to ensure continued {microshift-short} operation. When {microshift-short} 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 {microshift-short} restart to perform a rotation. |
21 | | - |
22 | | -[IMPORTANT] |
23 | | -==== |
24 | | -If the rotated certificate is a {microshift-short} certificate authority (CA), then all of the signed certificates rotate. If you created any custom CAs, ensure the CAs manually rotate. |
25 | | -==== |
26 | | - |
27 | | -[id="microshift-st-certificate-rotation_{context}"] |
28 | | -=== Short-term certificates |
29 | | -The following situations describe {microshift-short} 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 {microshift-short} starts or restarts. |
36 | | - |
37 | | -. Automatic restart for rotation: |
38 | | -.. When a short-term certificate is more than 8 months old, {microshift-short} 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 {microshift-short} 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 {microshift-short} starts or restarts. |
49 | | - |
50 | | -. Automatic restart for rotation: |
51 | | -.. When a long-term certificate is more than 9 years old, {microshift-short} might automatically restart so that it can rotate and apply a new certificate. |
| 15 | +{microshift-short} restarts automatically in certain cases, depending on certificate age. |
0 commit comments