Veritas InfoScale™ for Kubernetes Environments 8.0.220 - Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Veritas InfoScale on OpenShift
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Installing Veritas InfoScale on Kubernetes
- Prerequisites
- Tagging the InfoScale images on Kubernetes
- Installing InfoScale on Kubernetes
- Configuring KMS-based Encryption on an OpenShift cluster
- Configuring KMS-based Encryption on a Kubernetes cluster
- InfoScale CSI deployment in Container environment
- Dynamic provisioning
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Installing and configuring InfoScale DR Manager on OpenShift
- Installing and configuring InfoScale DR Manager on Kubernetes
- Disaster Recovery scenarios
- Configuring InfoScale
- Administering InfoScale on Containers
- Upgrading InfoScale
- Troubleshooting
Undeploying and uninstalling InfoScale
You can run the following command to undeploy and uninstall InfoScale on your Kubernetes cluster.
Note:
If you want to retain the disk group and re-use the Volumes you created, ensure that you note the ClusterID
before undeploying and uninstalling InfoScale. You must use this ClusterID
while re-installing InfoScale. Else, clean the disks before uninstalling.
kubectl delete -f /YAML/Kubernetes/cr.yaml
The commands to clean up InfoScale components like the Operator, SR, and SRO are as under
Note:
Run these commands only after all InfoScale pods are terminated.
kubectl delete -f /YAML/Kubernetes/iso.yaml
kubectl delete -f /YAML/Kubernetes/license_cr.yaml
kubectl delete -f /YAML/Kubernetes/lico.yaml
kubectl delete -f /YAML/Kubernetes/sr.yaml
kubectl delete -f /YAML/Kubernetes/sro.yaml
Note:
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.