Search <book_title>...

InfoScale™ 9.0 Support for Containers - Linux

Last Published: 2025-04-14

Product(s): InfoScale & Storage Foundation (9.0)

Platform: Linux

Installing from OperatorHub by using Command Line Interface (CLI)

Complete the following steps.

Downloading YAML.tar

Download YAML.tar from the Arctera Download Center.
Untar YAML.tar.
After you untar YAML.tar, a folder /YAML/OpenShift/OLM/ is created and all files required for installation are available in the folder.
Note:
An OpenShift cluster already has a namespace openshift-operators. You can choose to install InfoScale in openshift-operators.

Optionally, you can configure a new user - infoscale-admin, associated with a Role-based Access Control ( RBAC) clusterrole defined in infoscale-admin-role.yaml, to deploy InfoScale and its dependent components. infoscale-admin as a user when configured has clusterwide access to only those resources needed to deploy InfoScale and its dependent components such as SRO/NFD/Cert Manager in the desired namespaces.

To provide a secure and isolated environment for InfoScale deployment and associated resources, the namespace associated with these resources must be protected from access of all other users (except super user of the cluster), with appropriate RBAC implemented.

Run the following commands on the bastion node to create a new user - infoscale-admin and a new project and assign role or clusterrole to infoscale-admin. You must be logged in as a super user.

Configuring a new user

oc new-project <New Project name>
A new project is created for InfoScale deployment.
oc adm policy add-role-to-user admin infoscale-admin
Following output indicates that administrator privileges are assigned to the new user - infoscale-admin within the new project.
```
clusterrole.rbac.authorization.k8s.io/admin added: "infoscale-admin"
```
oc apply -f /YAML/OpenShift/OLM/infoscale-admin-role.yaml
Following output indicates that a clusterrole is created.
```
clusterrole.rbac.authorization.k8s.io/infoscale-admin-role created
```
oc adm policy add-cluster-role-to-user infoscale-admin-role infoscale-admin
Following output indicates that a clusterrole created is associated with infoscale-admin.
```
clusterrole.rbac.authorization.k8s.io/infoscale-admin-role added:
          "infoscale-admin"
```

After creating this user, you can login as infoscale-admin to perform all operations involved in installing InfoScale, configuring cluster, and adding nodes.

Installing Operators

Run the following command on the bastion node.
Note:
Ignore this step if you want to install in openshift-operators.
oc create namespace infoscale-vtas
Review output similar to the following to verify whether the namespace is created successfully.
```
namespace/infoscale-vtas created
```
Run the following command on the bastion node to create subscription.
Note:
If you want to install InfoScale in openshift-operators, edit /YAML/OpenShift/OLM/infoscale-sub.yaml. Change namespace from infoscale-vtas to openshift-operators
oc create -f /YAML/OpenShift/OLM/infoscale-sub.yaml
Following output indicates a successful command run.
```
subscription.operators.coreos.com/infoscale-sds-operator created
```
Run the following command on the bastion node to create an operator group.
Note:
Ignore this step if you want to install in openshift-operators.
oc create -f /YAML/OpenShift/OLM/infoscale-og.yaml
Following output indicates a successful command run.
```
operatorgroup.operators.coreos.com/infoscale-opgroup created
```

Run the following command on the bastion node.

oc get sub,og -n infoscale-vtas

Following output indicates a successful command run.

NAME                                PACKAGE              
subscription.operators.coreos.com   infoscale-sds-operator   
/infoscale-sds-operator

SOURCE                CHANNEL
certified-operators   stable

NAME                                                   AGE
operatorgroup.operators.coreos.com/infoscale-opgroup   24s

Run the following command on the bastion node.

oc get ip -A

Use installation-name from the output similar to the following output.

NAMESPACE        NAME            
infoscale-vtas   <installation-name>

CSV                                        APPROVAL   APPROVED
openshift-special-resource-operator.4.9.0  Manual     false
-202111041612

Run the following command on the bastion node.
Note:
Do not include the angle brackets (< >) in the command.
oc patch installplan <installation-name> --namespace infoscale-vtas --type merge --patch '{"spec":{"approved":true}}'
Following output indicates a successful command run.
```
installplan.operators.coreos.com/<installation-name> patched
```

Run the following command on the bastion node.

oc get ip -A

Review output similar to the following . Check if APPROVED is true.

NAMESPACE        NAME            
infoscale-vtas   <installation-name>

CSV                                         APPROVAL   APPROVED
openshift-special-resource-operator.4.9.0   Manual     true
-202111041612

Run the following command on the bastion node to check the status of csv.

oc get csv

Components which are getting installed or are pending are listed, as under.

NAME             DISPLAY        VERSION              REPLACES   PHASE
cert-manager.v1.6.1        cert-manager              1.6.1    Installing
infoscale-sds-operator.
                v8.0.100  InfoScale™ SDS Operator   8.0.100  Installing
nfd.4.9.0-202111020858     Node Feature Discovery 4.9.0-202111020858  
                                                              Pending
openshift-special-resource Special Resource Operator 4.9.0-202111041612 
-operator.4.9.0-202111041612                                  Installing

Run the following command on the bastion node to check the status of operator group and subscription.

oc get og,sub -n infoscale-vtas

Review output similar to the following output for the status.

operatorgroup.operators.coreos.com/infoscale-opgroup   47m

NAME                                                                                                                 
subscription.operators.coreos.com/cert-manager-stable-community
-operators-openshift-marketplace                       
subscription.operators.coreos.com/infoscale-sds-operator                                                                  
subscription.operators.coreos.com/nfd-stable-redhat-operators
-openshift-marketplace                                   
subscription.operators.coreos.com/openshift-special-resource-operator-
stable-redhat-operators-openshift-marketplace

 PACKAGE                            SOURCE                CHANNEL
cert-manager                        community-operators   stable
infoscale-sds-operator                  certified-operators   stable
nfd                                 redhat-operators      stable
openshift-special-resource-operator redhat-operators      stable

Run the following command on the bastion node again.

oc get csv

Review the output if all components are installed successfully.

NAME             DISPLAY        VERSION              REPLACES   PHASE
cert-manager.v1.6.1        cert-manager              1.6.1    Succeeded
infoscale-sds-operator.
                 v8.0.100  InfoScale™ SDS Operator   8.0.100  Succeeded
nfd.4.9.0-202111020858     Node Feature Discovery 4.9.0-202111020858 
                                                              Succeeded
openshift-special-resource Special Resource Operator 4.9.0-202111041612   
-operator.4.9.0-202111041612                                  Succeeded

After a successful installation of these components, create a NodeFeatureDiscovery CR. NodeFeatureDiscovery.yaml is a NodeFeatureDiscovery Custom Resource (CR).
Run the following command on the bastion node.
Note:
If you want to install InfoScale in openshift-operators, edit /YAML/OpenShift/OLM/NodeFeatureDiscovery.yaml. Change namespace from infoscale-vtas to openshift-operators for the nfd instance.
oc create -f /YAML/OpenShift/OLM/NodeFeatureDiscovery.yaml
Following output indicates a successful creation.
```
nodefeaturediscovery.nfd.openshift.io/nfd-instance created
```

Run the following command to check the status of all operator pods in infoscale-vtas.

Note:

If you have installed in openshift-operators, run oc get pods -n openshift-operators.

oc get pods -n infoscale-vtas

NAME                                   READY STATUS    RESTARTS   AGE
cert-manager-64c9cb7499-ppgbk          1/1   Running   0          165m
cert-manager-cainjector-5596f8f575
                                -2f246 1/1   Running   0          165m
cert-manager-webhook-7485d9dd59-864l4  1/1   Running   0          165m
infoscale-sds-operator-6dd8d77bf8-qwg2p 1/1  Running   0          165m
nfd-controller-manager-5fc85ff79-gx4qb 2/2   Running   0          165m
nfd-master-6zs5p                       1/1   Running   0          55m
nfd-master-ktc7s                       1/1   Running   0          55m
nfd-master-n2dh9                       1/1   Running   0          55m
nfd-worker-795vs                       1/1   Running   0          55m
nfd-worker-8n2m9                       1/1   Running   0          55m
nfd-worker-9j845                       1/1   Running   0          55m
nfd-worker-vwkwq                       1/1   Running   0          55m
special-resource-controller-manager-
dc5d6b768-2sk4k                        2/2   Running   0          165m

Applying Licenses

Run oc create -f /YAML/OpenShift/OLM/lico.yaml on the bastion node.
Run oc get pods -n infoscale-vtas|grep -i licensing on the bastion node to verify whether lico.yaml is successfully applied.
An output similar to the following indicates that lico.yaml is successfully applied.
```
NAME                                  READY STATUS  RESTARTS AGE
licensing-operator-fbd8c7dc4-rcfz5    1/1   Running 0        2m
```
After lico.yaml is successfully applied, licensing endpoints must be available.
Run oc describe service/lico-webhook-service -n infoscale-vtas|grep Endpoints on the master node and review the output.
Run the command again till you get an output in the following format.
```
Endpoints: <IP address of the endpoint>:<Port number>
```
Edit /YAML/OpenShift/OLM/license_cr.yaml for the license edition. The default license edition is Developer. You can change the licenseEdition. If you want to configure Disaster Recovery (DR), you must have Trialware or SubscriptionEnterprise as the license edition.
```
apiVersion: vlic.veritas.com/v1
kind: License
metadata:
  name: license-dev
spec:
  # valid licenseEdition values are Developer, Trialware, 
             SubscriptionStorage or SubscriptionEnterprise
  licenseEdition: "Developer"
```
Run oc create -f /YAML/OpenShift/OLM/license_cr.yaml on the bastion node.
Run oc get licenses on the bastion node to verify whether licenses have been successfully applied.
An output similar to the following indicates that license_cr.yaml is successfully applied.
```
NAME          NAMESPACE   LICENSE-EDITION   AGE
license                   DEVELOPER         27s
```