Search <book_title>...

Veritas InfoScale™ for Kubernetes Environments 8.0.200 - Linux

Last Published: 2023-02-21

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

Platform: Linux

Installing from OperatorHub by using Command Line Interface (CLI)

Complete the following steps.

Downloading YAML_8.0.200.tar.gz

Download YAML_8.0.200.tar.gz from the Veritas Download Center.
Unzip and untar YAML_8.0.200.tar.gz .
After you unzip and untar YAML_8.0.200.tar.gz , 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. cert-manager (Red Hat-certified) must be already installed for a successful installation of InfoScale.

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 deploy InfoScale licensing operator subscription.
oc create -f licensing-sub.yaml
Following output indicates a successful command run.
```
subscription.operators.coreos.com
  /infoscale-licensing-operator-sub 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                                                                 
subscription.operators.coreos.com/infoscale-licensing-operator-sub   
subscription.operators.coreos.com/infoscale-sds-operator-sub

PACKAGE                        SOURCE                CHANNEL
infoscale-licensing-operator   certified-operators   stable
infoscale-sds-operator         certified-operators   stable

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

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          CSV                     APPROVAL APPROVED
infoscale-vtas install-59vpz nfd.4.10.0-202206010607 Manual   false
infoscale-vtas install-wspfv infoscale-sds-operator. Manual   false
                             v8.0.200

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                                   InfoScale Licensing Operator                  
infoscale-sds-operator.v8.0.200        InfoScale™ SDS Operator                       
nfd.4.10.0-202206010607                Node Feature Discovery Operator              
openshift-cert-manager.v1.7.1          cert-manager Operator for 
                                       Red Hat OpenShift           
openshift-special-
resource-operator.4.10.0 -202206171549 Special Resource Operator

VERSION               REPLACES PHASE
8.0.200                        Installing
8.0.200                        Installing
4.10.0-202206010607            Installing
1.7.1-1                        Succeeded
4.10.0-202206171549            Pending

Run the following command on the bastion node again till all operators are installed successfully.

oc get csv

Review output as under.

NAME                                    DISPLAY                                       
infoscale-licensing-operator.v8.0.200   InfoScale Licensing Operator                  
infoscale-sds-operator.v8.0.200         InfoScale™ SDS Operator                       
nfd.4.10.0-202206010607                 Node Feature Discovery Operator               
openshift-cert-manager.v1.7.1           cert-manager Operator for 
                                        Red Hat OpenShift   
openshift-special-
  resource-operator.4.10.0-202206171549 Special Resource Operator

VERSION               REPLACES      PHASE
8.0.200                             Succeeded
8.0.200                             Succeeded
4.10.0-202206010607                 Succeeded
1.7.1-1                             Succeeded
4.10.0-202206171549                 Succeeded

Access your web console. Follow steps 10 to 15 in Installing from OperatorHub by using web console to install NodeFeatureDiscovery.

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

Edit /YAML/OpenShift/license_cr.yaml for the license edition. Optionally, you can change the license name. The default license edition is Developer. You can change the licenseEdition. If you want to configure Disaster Recovery (DR), you must have Enterprise as the license edition.
See Licensing.
```
apiVersion: vlic.veritas.com/v1
kind: License
metadata:
  name: license-dev
spec:
  # valid licenseEdition values are Developer, 
             Storage or Enterprise
  licenseEdition: "Developer"
  licenseServer: <Optional - IP address of
                  the VIOM server on your system>
```
Run oc create -f /YAML/OpenShift/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
```