2.2. Propagating changes
After you configure trusted CAs, you must make Red Hat Advanced Cluster Security for Kubernetes services trust them.
- If you have configured trusted CAs after the installation, you must restart Central.
- Additionally, if you are also adding certificates for integrating with image registries, you must restart both Central and Scanner.
2.2.1. Restarting the Central container 复制链接链接已复制到粘贴板!
You can restart the Central container by deleting the Central pod.
If you use Kubernetes, enter kubectl instead of oc.
Procedure
To delete the Central pod, run the following command:
$ oc -n stackrox delete pod -lapp=central
2.2.2. Restarting the Scanner container 复制链接链接已复制到粘贴板!
You can restart the Scanner container by deleting the pod.
Procedure
Run the following command to delete the Scanner pod:
On OpenShift Container Platform:
$ oc delete pod -n stackrox -l app=scannerOn Kubernetes:
$ kubectl delete pod -n stackrox -l app=scanner
After you have added trusted CAs and configured Central, the CAs are included in any new Sensor deployment bundles that you create.
- If an existing Sensor reports problems while connecting to Central, you must generate a Sensor deployment YAML file and update existing clusters.
If you are deploying a new Sensor using the
sensor.shscript, run the following command before you run thesensor.shscript:$ ./ca-setup-sensor.sh -d ./additional-cas/- If you are deploying a new Sensor using Helm, you do not have to run any additional scripts.