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 InfoScale by using the plugin

On an already deployed Kubernetes cluster with storage provisioned, you can download the InfoScale installers and install InfoScale. When you download the installers, a plugin is downloaded with which you can deploy the mandatory operators and then configure an InfoScale cluster.

As a prerequisite, git must be installed on the system. To enable autocompletion of commands on the bash shell, see the documentation of bash, fish, powershell, and zsh. These are the supported shells. Run kubectl-infoscale completion bash/fish/zsh/powershell --help for help.

Download kubectl_plugin_8.0.220.tar.gz from the Veritas Download Center and extract the tar file.
Copy kubectl-plugin binary at a $PATH location.

On a Kubernetes cluster, run the following command to download the InfoScale tar file.

kubectl-infoscale fetch-yaml

Note:

With this command the latest installer is downloaded.

The following output indicates a successful download

successfully downloaded InfoScale 8.0.220

You can run the following commands.

configure	Configures Kubernetes cluster
delete	Deletes InfoScale cluster along with the third-party dependencies.
deploy	Deploys InfoScale cluster with operators along with third-party dependencies.
show	Shows commands for displaying various operations.
get-available-infoscale-version	Gets available InfoScale versions from SORT.
help	Displays help on the available commands.
scale	Scales up the InfoScale cluster. (Adds storage)

Run the following command to deploy operators which are mandatory for InfoScale deployment.
kubectl-infoscale deploy dependent-operators
Review output as under
```
Step 1/2 started 
 Deploying: cert-manager
Step 2/2 started 
 Deploying: node-feature-discovery
```
Run the following command to verify whether the dependent operators are installed successfully.
kubectl-infoscale show get-resource-info --namespace cert-manager, node-feature-discovery
Run the following command to deploy licensing and InfoScale operators.
kubectl-infoscale deploy operator --image-registry <registry_name>
An example of a registry name is infoscale_registry.vxindia.veritas.com/8_0_200/lxrt-8.0-vike2-2022-10-13b/veritas.
Review output similar to the following.
```
Step 1/2 started 
 Deploying: infoscale-licensing-operator
Step 2/2 started 
 Deploying: infoscale-sds-operator
```

Run the following command to verify whether licensing and InfoScale operators are installed successfully.

kubectl-infoscale show get-resource-info --namespace infoscale-vtas

Review output similar to the following.

Deployment State: Ready

Resource: all           Namespace: infoscale-vtas
NAME                            READY   STATUS    RESTARTS   AGE
pod/infoscale-licensing
      -operator-c895d9dd8-lpzdl 1/1     Running   0          3d3h
pod/infoscale-sds-operator
       -55c78f4db9-pmh85        1/1     Running   0          3d3h

NAME                 TYPE      CLUSTER-IP    EXTERNAL-IP PORT(S)   
service/
iso-webhook-service  ClusterIP 10.99.89.137  <none>      443/TCP   
service/
lico-webhook-service ClusterIP 10.107.252.17 <none>      443/TCP   

AGE

3d4h

3d4h

NAME                         READY   UP-TO-DATE AVAILABLE AGE
deployment.apps/
infoscale-licensing-operator 1/1     1          1         3d4h
deployment.apps/
infoscale-sds-operator       1/1     1          1         3d4h

NAME                                    DESIRED CURRENT READY AGE
replicaset.apps/
infoscale-licensing-operator-c895d9dd8  1       1       1    3d3h
replicaset.apps/
infoscale-licensing-operator-d9fccb946  0       0       0    3d4h
replicaset.apps/
infoscale-sds-operator-55c78f4db9       1       1       1     3d3h
replicaset.apps/
infoscale-sds-operator-5dd857d6c6       0       0       0     3d4h

Copy the following node information into a file and save the file at an appropriate location

 - nodeName: <Name of first node>
    excludeDevice:
    - <Device path of this disk you want exclude 
                               from the Infoscale disk group>
    - <Device path of this disk you want exclude 
                               from the Infoscale disk group>
    fencingDevice:
    - <Device path of this disk you want add as fencing device>
    - <Device path of this disk you want add as fencing device>
 - nodeName: <Name of second node>
    excludeDevice:
    - <Device path of this disk you want exclude
                               from the Infoscale disk group>
    - <Device path of this disk you want exclude 
                                from the Infoscale disk group>
    fencingDevice:
    - <Device path of this disk you want add as fencing device>
    - <Device path of this disk you want add as fencing device>
.
.
.
YOU CAN ADD UPTO 16 NODES

Note:

excludeDevice and fencingDevice are optional parameters.

Run the following command to deploy an InfoScale cluster.

kubectl-infoscale deploy cluster --image-registry <image-registry> --license-edition <Developer/Storage/Enterprise> --cluster-id <Cluster ID> --cluster-name <Cluster Name> --node-info-file <Name of the file with the path>

Parameters listed in the following table are optional. You can add any of these parameters to the command as --<parameter name > <parameter value>.

`cluster-id`	ID of the cluster
`enable-scsi3pr`	Enable scsi3pr. The default value is false. You can set it to true as `--enable-scsi3pr=true`.
`encrypted`	Enable encryption at the disk group level. The default value is false. You can set it to true.
`isSharedStorage`	You can set it to true if you want to create a disk group by using storage available across nodes. The default value is false.
`sameEncKey`	You can set it to false if you want a different encryption key for every Volume. The default value is true.
`kubeconfig`	Path to the `kubeconfig` file which is used for CLI requests
`verbose`	Set log level from 0 to 5.

Review output similar to the following to verify whether the cluster is deployed successfully.

Step 1/2 started 
 Deploying: licence_cr
Step 2/2 started 
 Deploying: infoscale_cr

Run the following command to verify the status of the cluster and the SDS container pods.
kubectl-infoscale show get-resource-info --namespace infoscale-vtas

Viewing disk group information

To view information about the disk group that is created, run the following command.

kubectl-infoscale show storage-info

Review output similar to the following.

Disk Group Summary:
DiskList:  
node000_vmdk0_0  node000_vmdk0_1  node000_vmdk0_2  
node000_vmdk0_3  node000_vmdk0_4  node000_vmdk0_5  
.
.
Name: <Disk group name>
State: imported
TotalSize: 239.24g
FreeSize: 219.11g

Disk Information:
{"diskName":"node001_vmdk0_3","lunSize":"10.00g","mediaType":"hdd"} 
{"diskName":"node001_vmdk0_7","lunSize":"10.00g","mediaType":"hdd"} 
.
.

Adding storage to an InfoScale cluster

Create and save a new node information file as under. Ensure that it is different from the file you used while creating the cluster.

- nodeName: <Name of node you want to add>
    excludeDevice:
    - <Device path of this disk you want exclude 
                                from the Infoscale disk group>
    - <Device path of this disk you want exclude 
                                from the Infoscale disk group>
    fencingDevice:
    - <Device path of this disk you want add as fencing device>
    - <Device path of this disk you want add as fencing device>
.
.
.YOU CAN ADD MULTIPLE NODES.

Run the following command to deploy the new nodes.
kubectl-infoscale scale up node --node-info-file <Name of the new file with the path>
Review output as under.
```
Step 1/2 started 
 Deploying: infoscale_cr
```
You have successfully scaled up nodes of the InfoScale cluster. With the next step, storage is added and storage is scaled up.
Run the following command to add storage.
kubectl-infoscale scale up storage
Review output as under.
```
Step 1/2 started 
 Deploying: infoscale_cr
```

Undeploying and uninstalling InfoScale cluster

Run the following commands to undeploy and uninstall the InfoScale cluster with all the installed operators.
kubectl-infoscale delete cluster
kubectl-infoscale delete operator
kubectl-infoscale delete dependent-operators
Note:
Ensure that you run the command in the same order as mentioned here. After uninstallation, ensure that stale InfoScale kernel modules (vxio/vxdmp/veki/vxspec/vxfs/odm/glm/gms) do not remain loaded on any of the worker nodes. Rebooting a worker node deletes all such modules. When fencing is configured, certain keys are configured. Those must also be deleted after uninstallation. Run ./clearkeys.sh <Path to the first disk>, <Path to the second disk>,... to remove stale keys that might have remained.