Description

This article outlines the required prechecks for performing a storage scale-up in the IKE (Infoscale for Kubernetes) environment running on OpenShift.

1. LUN Mapping Verification

• Ensure that all new LUNs are mapped to each OpenShift worker node.

• Validate that the new disks are visible at the OS level on each node.

2. Pod Health Check

• Verify that all pods in the infoscale-vtas namespace are running without issues.

  # oc get pods -n infoscale-vtas

3. Infoscale Cluster Status

• Check the health of the Infoscale cluster and review any events that may be in a stuck or abnormal state.

  # oc describe infoscalecluster -n infoscale-vtas

a. Identify Running SDS Pods

Use the following command to list all active SDS pods:

#oc get pods -n infoscale-vtas | grep -i sds | grep -v operator

b. Access a Running SDS Pod

# oc exec -it -n infoscale-vtas -- bash

Replace   with the actual pod name.

c. Check Disk Status

Inside the SDS pod, list all disks and review their states:

#/opt/VRTSvcs/bin/hacli -cmd 'vxdisk list'

All planned new disks need to be in online invalid state.

5. Exclude Unused Storage Devices

Exclude any additional or unrelated storage products (e.g., external arrays not used by VIKE):

#vxdmpadm exclude product=:

A UDID is generated for every device discovered by Volume Manager and is composed of the following information:

• Vendor ID (VID)
• Product ID (PID)
• Cabinet Serial Number (Array serial number)
• LUN Serial Number (Serial number for LUN on array)

Two strings are visible in vxdisk -v list (device) output:

# vxdisk -p list emc_clariion0_345 | egrep -i 'VID|PID'
VID                 : DGC
PID                 : VRAID
Example:

#vxdmpadm exclude product=DGC:VRAID   

Note: The product will be different, so make sure to use the correct name.

6. Maxgrow Process Check

Check if there are any excessive maxgrow processes running, which may affect parallel operations:

#/opt/VRTSvcs/bin/hacli -cmd 'ps -ef | grep maxgrow'

Investigate if a high number of these processes are found.

7. Annotate for Storage Scale-Up

Once all checks are completed and the environment is healthy, trigger the storage scale-up by annotating the InfoscaleCluster

# oc annotate infoscalecluster -n infoscale-vtas infoscale.veritas.com/storage-scale-up='enabled'

Replace  with the actual name of the InfoscaleCluster resource.