此内容没有您所选择的语言版本。

Chapter 4. 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.

Note

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

4.1. Next steps

Install an OpenShift Container Platform cluster:

Red Hat logoGithubRedditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

© 2024 Red Hat, Inc.