OpenShift via OperatorHub
⚠️ Make sure the prerequisites for Ondat are satisfied before proceeding. Including the deployment of an etcd cluster and configuration of CRI-O PID limits.
⚠️ If you have installed OpenShift in AWS ensure that the requisite ports are opened for the worker nodes' security group.
💡 For OpenShift upgrades, refer to the OpenShift platform page.
Ondat v2 supports OpenShift v4. For more information, see the OpenShift platform page.
installation of Ondat via OperatorHub
Step 1: Operatorhub
OperatorHubfrom the Catalog sub menu and search for StorageOS
💡 Choose between using the RedHat Marketplace or the Community Operators installation.
Select StorageOS and click Install.
Select the relevant install options.
Make sure the
Approval Strategyis set to Manual. This option makes sure that the StorageOS Operator doesn’t upgrade versions without explicit approval.
Start the approval procedure by clicking on the operator name.
On Subscription Details, click the approval link.
On Review Manual Install panel in the Components tab, click Approve to confirm the installation.
The Ondat Operator is installed along the required CRDs.
Step 2: Authentication
Create a Secret in the
openshift-operatorsproject and select the YAML option to create a secret containing the
passwordkey. The username and password defined in the secret will be used to authenticate when using the Ondat CLI and GUI. Take note of which project you created the secret in.
Input the secret as YAML for simplicity.
apiVersion: v1 kind: Secret metadata: name: storageos-api namespace: openshift-operators type: "kubernetes.io/storageos" data: # echo -n '<secret>' | base64 username: c3RvcmFnZW9z password: c3RvcmFnZW9z
Go to the Operators->Installed Operators and verify that the StorageOS Operator is installed.
Go to the StorageOS Cluster section.
Click Create StorageOSCluster.
💡 An Ondat Cluster is defined using a Custom Resource Definition
Create the Custom Resource
The StorageOS cluster resource describes the Ondat cluster that will be created. Parameters such as the
specparameters are available on the Operator configuration page.
apiVersion: "storageos.com/v1" kind: StorageOSCluster metadata: name: storageos namespace: openshift-operators spec: # Ondat Pods are in kube-system by default secretRefName: "storageos-api" # Reference the Secret created in the previous step secretRefNamespace: "openshift-operators" # Namespace of the Secret created in the previous step k8sDistro: "openshift" kvBackend: address: 'storageos-etcd-client.etcd:2379' # Example address, change for your etcd endpoint # address: '10.42.15.23:2379,10.42.12.22:2379,10.42.13.16:2379' # You can set ETCD server ips resources: requests: memory: "512Mi" cpu: 1 # nodeSelectorTerms: # - matchExpressions: # - key: "node-role.kubernetes.io/worker" # Compute node label will vary according to your installation # operator: In # values: # - "true"
Verify that the StorageOS Cluster resource status is Running.
It can take up to a minute to report the Ondat Pods ready.
Check the StorageOS Pods in the
A Status of 3/3 in the Ready column for the Daemonset Pods indicates that Ondat is bootstrapped successfully.
⚠️ Newly installed Ondat clusters must be licensed within 24 hours. Our Community Edition tier supports up to 1TiB of provisioned storage.
To obtain a license, follow the instructions on our licensing operations page.
First Ondat volume
If this is your first installation you may wish to follow the Ondat volume guide for an example of how to mount an Ondat volume in a Pod.