Please enter search query.
Search <book_title>...
Veritas InfoScale™ for Kubernetes Environments 8.0.100 - Linux
Last Published:
2022-07-11
Product(s):
InfoScale & Storage Foundation (8.0.100)
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Veritas InfoScale on OpenShift
- Introduction
- Prerequisites
- Additional Prerequisites for Azure RedHat OpenShift (ARO)
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Installing Veritas InfoScale on Kubernetes
- Tech Preview: Configuring KMS-based Encryption on an OpenShift cluster
- Tech Preview: Configuring KMS-based Encryption on a Kubernetes cluster
- InfoScale CSI deployment in Container environment
- CSI plugin deployment
- Static provisioning
- Dynamic provisioning
- Resizing Persistent Volumes (CSI volume expansion)
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Using InfoScale with non-root containers
- Using InfoScale in SELinux environments
- CSI Drivers
- Creating CSI Objects for OpenShift
- Installing and configuring InfoScale DR Manager on OpenShift
- Installing and configuring InfoScale DR Manager on Kubernetes
- Disaster Recovery scenarios
- Configuring InfoScale
- Troubleshooting
Undeploying and uninstalling InfoScale
You can run the following command to undeploy and uninstall InfoScale on your Kubernetes cluster.
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.