2.4. Creating an OpenShift Data Foundation cluster

Procedure

1. In the OpenShift Web Console, click Operators Installed Operators to view all the installed operators.

   Ensure that the Project selected is openshift-storage.

2. Click on the OpenShift Data Foundation operator, and then click Create StorageSystem.

3. In the Backing storage page, select the following:

   1. Select Full Deployment for the Deployment type option.
   2. Select the Use an existing StorageClass option.

   3. Select the Storage Class.

      By default, it is set to thin-csi. If you have created a storage class with zeroedthick or eagerzeroedthick disk format for thick-provisioned storage, then that storage class is listed in addition to the default, thin-csi storage class.

   4. Optional: Select Use external PostgreSQL checkbox to use an external PostgreSQL [Technology preview].

      This provides high availability solution for Multicloud Object Gateway where the PostgreSQL pod is a single point of failure.

      중요

      OpenShift Data Foundation ships PostgreSQL images maintained by Red Hat, which are used to store metadata for the Multicloud Object Gateway. This PostgreSQL usage is at the application level.

      As a result, OpenShift Data Foundation does not perform database-level optimizations or in-depth insights.

      If customers have their own PostgreSQL that is well-maintained and optimized, we recommend using it. OpenShift Data Foundation supports external PostgreSQL instances.

      Any PostgreSQL-related issues requiring code changes or deep technical analysis may need to be addressed upstream. This could result in longer resolution times.

      1. Provide the following connection details:

         • Username
         • Password
         • Server name and Port
         • Database name
      2. Select Enable TLS/SSL checkbox to enable encryption for the Postgres server.
   5. Click Next.

4. In the Capacity and nodes page, provide the necessary information:

   1. Select a value for Requested Capacity from the dropdown list. It is set to 2 TiB by default.

      참고

      Once you select the initial storage capacity, cluster expansion is performed only using the selected usable capacity (three times of raw storage).

   2. In the Select Nodes section, select at least three available nodes.

   3. In the Configure performance section, select one of the following performance profiles:

      • Lean

        Use this in a resource constrained environment with minimum resources that are lower than the recommended. This profile minimizes resource consumption by allocating fewer CPUs and less memory.

      • Balanced (default)

        Use this when recommended resources are available. This profile provides a balance between resource consumption and performance for diverse workloads.

      • Performance

        Use this in an environment with sufficient resources to get the best performance. This profile is tailored for high performance by allocating ample memory and CPUs to ensure optimal execution of demanding workloads.

        참고

        You have the option to configure the performance profile even after the deployment using the Configure performance option from the options menu of the StorageSystems tab.

        중요

        Before selecting a resource profile, make sure to check the current availability of resources within the cluster. Opting for a higher resource profile in a cluster with insufficient resources might lead to installation failures.

        For more information about resource requirements, see Resource requirement for performance profiles.

   4. Optional: Select the Taint nodes checkbox to dedicate the selected nodes for OpenShift Data Foundation.

      + Spread the worker nodes across three different physical nodes, racks, or failure domains for high availability.

      + Use vCenter anti-affinity to align OpenShift Data Foundation rack labels with physical nodes and racks in the data center to avoid scheduling two worker nodes on the same physical chassis.

      + If the nodes selected do not match the OpenShift Data Foundation cluster requirement of the aggregated 30 CPUs and 72 GiB of RAM, a minimal cluster is deployed. For minimum starting node requirements, see the Resource requirements section in the Planning guide.

      + Select the Taint nodes checkbox to make selected nodes dedicated for OpenShift Data Foundation.

   5. Click Next.

5. Optional: In the Security and network page, configure the following based on your requirements:

   1. To enable encryption, select Enable data encryption for block and file storage.

      1. Select either one or both the encryption levels:

         • Cluster-wide encryption

           Encrypts the entire cluster (block and file).

         • StorageClass encryption

           Creates encrypted persistent volume (block only) using encryption enabled storage class.

      2. Optional: Select the Connect to an external key management service checkbox. This is optional for cluster-wide encryption.

         1. From the Key Management Service Provider drop-down list, either select Vault or Thales CipherTrust Manager (using KMIP). If you selected Vault, go to the next step. If you selected Thales CipherTrust Manager (using KMIP), go to step iii.

         2. Select an Authentication Method.

            Using Token authentication method

            • Enter a unique Connection Name, host Address of the Vault server ('https://<hostname or ip>'), Port number and Token.

            • Expand Advanced Settings to enter additional settings and certificate details based on your Vault configuration:

              • Enter the Key Value secret path in Backend Path that is dedicated and unique to OpenShift Data Foundation.
              • Optional: Enter TLS Server Name and Vault Enterprise Namespace.
              • Upload the respective PEM encoded certificate file to provide the CA Certificate, Client Certificate and Client Private Key .
              • Click Save and skip to step iv.

            Using Kubernetes authentication method

            • Enter a unique Vault Connection Name, host Address of the Vault server ('https://<hostname or ip>'), Port number and Role name.

            • Expand Advanced Settings to enter additional settings and certificate details based on your Vault configuration:

              • Enter the Key Value secret path in Backend Path that is dedicated and unique to OpenShift Data Foundation.
              • Optional: Enter TLS Server Name, Authentication Path, and Vault Enterprise Namespace if applicable.
              • Upload the respective PEM encoded certificate file to provide the CA Certificate, Client Certificate and Client Private Key .
              • Click Save and skip to step iv.

         3. To use Thales CipherTrust Manager (using KMIP) as the KMS provider, follow the steps below:

            1. Enter a unique Connection Name for the Key Management service within the project.

            2. In the Address and Port sections, enter the IP of Thales CipherTrust Manager and the port where the KMIP interface is enabled. For example:

               • Address: 123.34.3.2
               • Port: 5696
            3. Upload the Client Certificate, CA certificate, and Client Private Key.
            4. If StorageClass encryption is enabled, enter the Unique Identifier to be used for encryption and decryption generated above.
            5. The TLS Server field is optional and used when there is no DNS entry for the KMIP endpoint. For example, kmip_all_<port>.ciphertrustmanager.local.
         4. Select a Network.
         5. Click Next.

   2. To enable in-transit encryption, select In-transit encryption.

      1. Select a Network.
      2. Click Next.
6. In the Data Protection page, if you are configuring Regional-DR solution for Openshift Data Foundation then select the Prepare cluster for disaster recovery (Regional-DR only) checkbox, else click Next.

7. In the Review and create page, review the configuration details.

   To modify any configuration settings, click Back.

8. Click Create StorageSystem.