Chapter 2. Adding trusted certificate authorities


Learn how to add custom trusted certificate authorities to Red Hat Advanced Cluster Security for Kubernetes.

2.1. Overview of adding trusted CAs

If you are using an enterprise certificate authority (CA) on your network, or self-signed certificates, you must add the CA’s root certificate to Red Hat Advanced Cluster Security for Kubernetes as a trusted root CA.

Adding trusted root CAs allows:

  • Central and Scanner to trust remote servers when you integrate with other tools.
  • Sensor to trust custom certificates you use for Central.

You can add additional CAs during the installation or on an existing deployment.

Note

You must first configure your trusted CAs in the cluster where you have deployed Central and then propagate the changes to Scanner and Sensor.

2.2. Configuring additional CAs

You can add custom certificate authorities (CAs) to Red Hat Advanced Cluster Security for Kubernetes by using the ca-setup.sh script to configure single or multiple CA certificates.

Procedure

  1. Download the ca-setup.sh script.

    Note
    • If you are doing a new installation, you can find the ca-setup.sh script in the scripts directory at central-bundle/central/scripts/ca-setup.sh.
    • You must run the ca-setup.sh script in the same terminal from which you logged into your OpenShift Container Platform cluster.
  2. Make the ca-setup.sh script executable:

    $ chmod +x ca-setup.sh
  3. Add the certificates by using one of the following options:

    1. To add a single certificate, use the -f option to specify the certificate file:

      $ ./ca-setup.sh -f <certificate>
      Note
      • You must use a PEM-encoded certificate file. The file can have any extension.
      • To update a certificate that you added before, use the -u option along with the -f option.
    2. To add many certificates at once, move all the certificates into a directory, and then use the -d option to specify that directory:

      $ ./ca-setup.sh -d <directory_name>
      Note
      • You must use PEM-encoded certificate files with a .crt or .pem extension.
      • Each file must contain only a single certificate.
      • To update certificates that you added before, use the -u option along with the -d option.

2.3. Propagating changes to services

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.3.1. Restarting the Central container

You can restart the Central container by deleting the Central pod.

Note

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.3.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=scanner
    • On Kubernetes:

      $ kubectl delete pod -n stackrox -l app=scanner

New Sensor deployment bundles automatically include the trusted CAs that you added, but an existing Sensor or a Sensor that you deploy by using the sensor.sh script requires additional action.

Important

After you have added trusted CAs and configured Central, any new Sensor deployment bundles that you create include the CAs.

  • 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.sh script, run the following command before you run the sensor.sh script:

    $ ./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.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top