Using InfoScale toolset

Last published : Jun 12, 2026
After you install InfoScale, InfoScale toolset yaml files are automatically downloaded. You can use these files to know the storage consumption or Volume rekey operations. The files are downloaded at templates/.
To know storage consumption
  1. Edit templates/storage/infoscale-storage-usage.yaml. You can specify the namespace and cluster. To know the storage consumption of all namespaces and clusters, do not specify anything in infoscale-storage-usage.yaml.
  2. Run the following command to apply infoscale-storage-usage.yaml.
kubectl/oc apply -f /templates/storage/infoscale-storage-usage.yaml
  1. Output similar to the following indicates success.
    certificate.cert-manager.io/infoscale-tools-cert created
    job.batch/infoscale-storage-usage created
    1. Run the following command to list storage consumption.
    kubectl/oc get po -n infoscale-vtas --sort-by=.metadata.creationTimestamp -o 'jsonpath={.items[-1].metadata.name}' | xargs kubectl/oc logs -n infoscale-vtas
    Review output similar to the following
    NAMESPACE       CLUSTER         DISKGROUP
    \<namespace\>     \<cluster name\> \<diskgroup name\>
STATE           VERSION    FREESIZE
imported shared <version> <Available disk space in GB>
    Disk information of Diskgroup-ID: \<ID of the diskgroup\>
 DISKS      DISKSIZE   MEDIATYPE
 \<disk id\> \<disk size\> \<disk type\>
.
.
.
.
.
.
ALL DISKGROUPS ARE LISTED
To enforce rekey operation on encrypted Volumes
  1. Run the following command to prepare PVC for enforced rekey operation.
kubectl/oc annotate pvc <PVC name> infoscale.veritas.com/rekey="true" --overwrite
The following command indicates that the PVC is ready for enforced rekey operation.
persistentvolumeclaim/\<PVC name\> annotated
  1. Run the following command to enforce rekey.
kubectl/oc apply -f /templates/rekey/infoscale-rekey-ondemand.yaml
To schedule rekey operation on encrypted Volumes
  1. Edit templates/rekey/infoscale-rekey-schedule.yaml to add schedule for rekey operation.
  2. Run the following command to apply the schedule.
kubectl/oc apply -f /templates/rekey/infoscale-rekey-schedule.yaml
Following output indicates a successful application of the schedule.
certificate.cert-manager.io/infoscale-tools-cert created
cronjob.batch/infoscale-rekey-schedule created
To perform a diskgroup rekey operation
  • Run the following command -
kubectl/oc apply -f /templates/rekey/infoscale-rekey-schedule.yaml
Note: After Disaster Recovery (DR) configuration, if rekey is performed on a Volume; the parametervxvm.attr.encwvekis not replicated from the primary to the secondary cluster. Althoughvxvm.attr.encwvekis different on the secondary cluster, Disaster Recovery (DR) operation takes place successfully.