Search <book_title>...

Veritas InfoScale™ for Kubernetes Environments 8.0.220 - Linux

Last Published: 2023-10-16

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

Platform: Linux

Installing by using YAML

Complete the following steps

Download YAML_8.0.220.tar.gz from the Veritas Download Center.
Unzip and untar YAML_8.0.220.tar.gz .
After you unzip and untar YAML_8.0.220.tar.gz , the folders /YAML/OpenShift/, /YAML/OpenShift/air-gapped-systems , /YAML/DR, and /YAML/Kubernetes are created. Each folder contains files required for installation.

Note:

cert-manager and Node Feature Discovery (both Red Hat-certified) must be already installed for a successful installation of InfoScale. To know how to install, see steps 10 to 15 of Installing from OperatorHub by using web console. Node Feature Discovery custom resource must also be created in the same namespace where Node Feature Discovery is installed.

Optionally, you can configure a new user - infoscale-admin, associated with a Role-based Access Control ( RBAC) clusterrole defined ininfoscale-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.

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/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"
```

You must now perform all installation-related activities by logging in as infoscale-admin. A cluster super-user can also install InfoScale.

As your system is connected with the Internet, you must login to the Red Hat registry before you install InfoScale. All information about the worker nodes must be added to the cr.yaml file. All worker nodes become part of InfoScale cluster after cr.yaml is applied.

Note:

After you download, unzip, and untar YAML_8.0.220.tar.gz , all files required for installation are available.

Applying Licenses

Run oc create -f /YAML/OpenShift/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
infoscale-licensing-operator
                  -fbd8c7dc4-rcfz5    1/1   Running 0        2m
```
After lico.yaml is successfully applied, Wait till the licensing endpoints are activated.
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/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
```

Complete the following steps to install iso.yaml.

Run the following command on all the worker nodes.
podman login registry.connect.redhat.com Username: {REGISTRY-SERVICE-ACCOUNT-USERNAME} Password: {REGISTRY-SERVICE-ACCOUNT-PASSWORD}
Wait for the message - Login successful.
Run the following command on the bastion node to install Veritas InfoScale.
oc create -f /YAML/OpenShift/iso.yaml
Run the following command on the bastion node to verify whether the installation is successful
oc get pods -n infoscale-vtas|grep infoscale-sds-operator
An output similar to the following indicates a successful installation. READY 1/1 indicates that Storage cluster resources can be created.
```
NAME                                   READY STATUS  RESTARTS AGE  
infoscale-sds-operator-bb55cfc4d-pclt5 1/1   Running 0        20h
```