3.2. Reissuing internal certificates for secured clusters
Secured clusters contain the Collector, Sensor, Admission Control, and local Scanner components. These components communicate with each other, and with Central by using certificates.
Choose the appropriate method to reissue the internal certificates:
- Use the automatic certificate renewal feature. This is the recommended method for Operator and Helm deployments.
-
Create, download, and install an init bundle on the secured cluster. You must have the
Adminuser role to create an init bundle. This method is only recommended for Operator and Helm deployments if the certificates have already expired and the secured cluster can no longer connect to Central. -
Use the automatic upgrades feature, which is only available for static manifest deployments by using the
roxctlCLI. This method is only recommended if you have a specific installation requirement that necessitates the use of this method.
Secured clusters contain the Collector, Sensor, Admission Control, and local Scanner components. You can reissue internal certificates for these components by using automatic certificate renewal.
TLS certificates are automatically renewed several months in advance but are only loaded when RHACS pods restart, for example, during an upgrade.
By viewing the Clusters page, you can verify that the automatic certificate renewal is active.
Procedure
-
In the RHACS portal, click Platform Configuration
Clusters. - Verify that Auto-refresh enabled appears in the Credential Expiration column.
If a secured cluster displays a warning about soon-to-expire credentials even though auto-refresh is enabled, you must manually restart the pods of the affected cluster to apply the latest certificates and prevent downtime.
For more information, see "Applying the latest internal certificates".
3.2.1.2. Applying the latest internal certificates 复制链接链接已复制到粘贴板!
By manually restarting the pods of the affected cluster, you can apply the latest certificates and prevent downtime.
If you use Kubernetes, use kubectl instead of oc.
Prerequisites
-
You have
writepermission for theAdministrationresource.
Procedure
To manually restart the pods of the affected cluster, run the following command:
$ oc -n <namespace> delete pods --allwhere:
<namespace>-
Specifies the namespace where you installed the secured cluster. For example,
stackrox.
Secured clusters contain the Collector, Sensor, Admission Control, and local Scanner components. These components use a built-in server certificate for authentication when communicating with other Red Hat Advanced Cluster Security for Kubernetes (RHACS) components.
The RHACS portal shows an information banner when the Central certificate is about to expire.
The information banner only appears 15 days before the certificate expiry date.
Prerequisites
-
You have
writepermission for theAdministrationresource. -
You have the
Adminuser role to create init bundles.
Store the init bundle securely because it contains secrets. You can use the same bundle on multiple secured clusters.
Procedure
Choose the appropriate method to generate an init bundle:
To generate an init bundle by using the user interface (UI), perform the following steps:
-
In the RHACS portal, click Platform Configuration
Clusters. - Click Init bundles.
- To create a new init bundle, click Create bundle.
- Enter a name for the cluster init bundle.
Choose the appropriate platform of the secured clusters:
The following values are associated with the platform of the secured clusters:
-
OpenShift -
EKS -
AKS -
GKE
-
Choose the appropriate installation method for the secured cluster services from the drop-down list:
The following values are associated with the installation method for the secured cluster services:
-
Operator (recommended) -
Helm chart
-
Click Download.
重要You can only download the YAML file once when you create an init bundle. Store the YAML file securely because it contains secrets.
-
In the RHACS portal, click Platform Configuration
To generate an init bundle by using the
roxctlCLI, run the following command:$ roxctl -e <endpoint> -p <admin_password> central \ init-bundles generate --output-secrets <bundle_name> \ init-bundle.yaml
To create the necessary resources on each secured cluster, run the following command:
$ oc -n stackrox apply -f <init-bundle.yaml>
Secured clusters contain the Collector, Sensor, Admission Control, and local Scanner components. You can reissue internal certificates for these components by using automatic upgrades.
Automatic upgrades are only applicable to static manifest-based deployments by using the roxctl CLI.
For more information, see "Install Central using the roxctl CLI".
Prerequisites
- You have enabled automatic upgrades for all the clusters.
-
You have
writepermission for theAdministrationresource.
Procedure
-
In the RHACS portal, click Platform Configuration
Clusters. - Select a cluster to view its details.
From the cluster details panel, select the link to Apply credentials by using an automatic upgrade.
注意When you apply an automatic upgrade, Red Hat Advanced Cluster Security for Kubernetes (RHACS) creates new credentials in the selected cluster. However, you continue to see a notification. The notification disappears when each RHACS service uses the new credentials after the service restarts.