Chapter 3. Deploy standalone Multicloud Object Gateway
Deploying only the Multicloud Object Gateway component with OpenShift Data Foundation provides the flexibility in deployment and helps to reduce the resource consumption. Use this section to deploy only the standalone Multicloud Object Gateway component, which involves the following steps:
- Installing Red Hat OpenShift Data Foundation Operator
- Creating standalone Multicloud Object Gateway
3.1. Installing Red Hat OpenShift Data Foundation Operator
You can install Red Hat OpenShift Data Foundation Operator using the Red Hat OpenShift Container Platform Operator Hub.
Access to an OpenShift Container Platform cluster using an account with
cluster-adminand Operator installation permissions.
- You must have at least three worker nodes in the Red Hat OpenShift Container Platform cluster.
- For additional resource requirements, see the Planning your deployment guide.
When you need to override the cluster-wide default node selector for OpenShift Data Foundation, you can use the following command in the command line interface to specify a blank node selector for the
openshift-storagenamespace (create openshift-storage namespace in this case):
$ oc annotate namespace openshift-storage openshift.io/node-selector=
Taint a node as
infrato ensure only Red Hat OpenShift Data Foundation resources are scheduled on that node. This helps you save on subscription costs. For more information, see How to use dedicated worker nodes for Red Hat OpenShift Data Foundation chapter in the Managing and Allocating Storage Resources guide.
- Log in to the OpenShift Web Console.
- Click Operators → OperatorHub.
Scroll or type
OpenShift Data Foundationinto the Filter by keyword box to find the OpenShift Data Foundation Operator.
- Click Install.
Set the following options on the Install Operator page:
- Update Channel as stable-4.9.
- Installation Mode as A specific namespace on the cluster.
Installed Namespace as Operator recommended namespace openshift-storage. If Namespace
openshift-storagedoes not exist, it is created during the operator installation.
Select Approval Strategy as Automatic or Manual.
If you select Automatic updates, then the Operator Lifecycle Manager (OLM) automatically upgrades the running instance of your Operator without any intervention.
If you select Manual updates, then the OLM creates an update request. As a cluster administrator, you must then manually approve that update request to update the Operator to a newer version.
- Ensure that the Enable option is selected for the Console plugin.
- Click Install.
We recommend using all default settings. Changing it may result in unexpected behavior. Alter only if you are aware of its result.
- Verify that the OpenShift Data Foundation Operator shows a green tick indicating successful installation.
After the operator is successfully installed, a pop-up with a message,
Web console update is availableappears on the user interface. Click Refresh web console from this pop-up for the console changes to reflect.
- In the Web Console, navigate to Operators and verify if OpenShift Data Foundation is available.
In case the console plugin option was not automatically enabled after you installed the OpenShift Data Foundation Operator, you need to enable it.
For more information on how to enable the console plugin, see Enabling the Red Hat OpenShift Data Foundation console plugin.
3.2. Creating standalone Multicloud Object Gateway
Use this section to create only the Multicloud Object Gateway component with OpenShift Data Foundation.
- Ensure that OpenShift Data Foundation Operator is installed.
- (For deploying using local storage devices only) Ensure that Local Storage Operator is installed.
- Ensure that you have a storage class and is set as the default.
In the OpenShift Web Console, click Operators → Installed Operators to view all the installed operators.
Ensure that the Project selected is
- Click OpenShift Data Foundation operator and then click Create StorageSystem.
- In the Backing storage page, expand Advanced.
- Select Multicloud Object Gateway for Deployment type.
- Click Next.
Optional: In the Security page, select Connect to an external key management service.
Key Management Service Provider is set to
- Enter Vault Service Name, host Address of Vault server ('https://<hostname or ip>'), Port number, and Token.
Expand Advanced Settings to enter additional settings and certificate details based on your
- Enter the Key Value secret path in the 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.
- Click Next.
- Key Management Service Provider is set to
In the Review and create page, review the configuration details:
To modify any configuration settings, click Back.
- Click Create StorageSystem.
- Verifying that the OpenShift Data Foundation cluster is healthy
- In the OpenShift Web Console, click Storage → OpenShift Data Foundation.
In the Status card of the Overview tab, click Storage System and then click the storage system link from the pop up that appears.
- In the Status card of the Object tab, verify that both Object Service and Data Resiliency have a green tick.
- In the Details card, verify that the MCG information is displayed.
- Verify the state of the pods
- Click Workloads → Pods from the OpenShift Web Console.
openshift-storagefrom the Project drop-down list and verify that the following pods are in
If the Show default projects option is disabled, use the toggle button to list all the default projects.
Component Corresponding pods
OpenShift Data Foundation Operator
ocs-operator-*(1 pod on any worker node)
ocs-metrics-exporter-*(1 pod on any worker node)
odf-operator-controller-manager-*(1 pod on any worker node)
odf-console-*(1 pod on any worker node)
(1 pod on any worker node)
Multicloud Object Gateway
noobaa-operator-*(1 pod on any worker node)
noobaa-core-*(1 pod on any worker node)
noobaa-db-pg-*(1 pod on any worker node)
noobaa-endpoint-*(1 pod on any worker node)