This is a cache of https://docs.openshift.com/container-platform/4.16/installing/installing_ibm_cloud_public/user-managed-encryption-ibm-cloud.html. It is a snapshot of the page at 2024-11-22T08:45:25.964+0000.
<strong>user</strong>-managed encryption - Installing on IBM Cloud | Installing | OpenShift Container Platform 4.16
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history bug_report picture_as_pdf
×

user-managed encryption for IBM Cloud

By default, provider-managed encryption is used to secure the following when you deploy an OpenShift Container Platform cluster:

  • The root (boot) volume of control plane and compute machines

  • Persistent volumes (data volumes) that are provisioned after the cluster is deployed

You can override the default behavior by specifying an IBM® Key Protect for IBM Cloud® (Key Protect) root key as part of the installation process.

When you bring our own root key, you modify the installation configuration file (install-config.yaml) to specify the Cloud Resource Name (CRN) of the root key by using the encryptionKey parameter.

You can specify that:

  • The same root key be used be used for all cluster machines. You do so by specifying the key as part of the cluster’s default machine configuration.

    When specified as part of the default machine configuration, all managed storage classes are updated with this key. As such, data volumes that are provisioned after the installation are also encrypted using this key.

  • Separate root keys be used for the control plane and compute machine pools.

For more information about the encryptionKey parameter, see Additional IBM Cloud configuration parameters.

Make sure you have integrated Key Protect with your IBM Cloud Block Storage service. For more information, see the Key Protect documentation.

Next steps

Install an OpenShift Container Platform cluster: