- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Kubernetes Overview
- Enabling the Kubernetes Cluster
- Managing Storage, Assets, and Protection for Kubernetes Clusters
- Restoring Kubernetes Namespaces and PVCs
- Kubernetes Cluster Best Practices and Troubleshooting
- Configuration changes required for use of optimized data path and first class disks
- Recommendations and considerations when using a Kubernetes cluster
- Support Network File System (NFS) root squashing
- Update the Velero or OADP version used by PowerProtect Data Manager
- VM Direct protection engine overview
- Troubleshooting network setup issues
- Troubleshooting Kubernetes cluster issues
- Specify volumesnapshotclass for v1 CSI snapshots
- Enabling protection when the vSphere CSI driver is installed as a process
- Customizing PowerProtect Data Manager pod configuration
- Backups fail or hang on OpenShift after a new PowerProtect Data Manager installation or update from a 19.9 or earlier release
- Data protection operations for high availability Kubernetes cluster might fail when API server not configured to send ROOT certificate
- Kubernetes cluster on Amazon Elastic Kubernetes Service certificate considerations
- Removing PowerProtect Data Manager components from a Kubernetes cluster
- Increase the number of worker threads in Supervisor cluster backup-driver if Velero timeout occurs
- Velero pod backup and restore might fail if namespace being protected contains a large number of resources
- Pull images from Docker Hub as authenticated user if Docker pull limits reached
- Application-Consistent Database Backups in Kubernetes
- About application-consistent database backups in Kubernetes
- Obtain and deploy the CLI package
- About application templates
- Deploy application templates
- Perform application-consistent backups
- Verify application-consistent backups
- Disaster recovery considerations
- Granular-level restore considerations
- Log truncation considerations
PowerProtect Data Manager 19.10 Kubernetes User Guide
Removing PowerProtect Data Manager components from a Kubernetes cluster
Review the following sections if you need to remove PowerProtect Data Manager components from the Kubernetes cluster:
Remove PowerProtect Data Manager components
Run the following commands to remove the PowerProtect Data Manager components:
- kubectl delete crd -l app.kubernetes.io/part-of=powerprotect.dell.com
- kubectl delete clusterrolebinding powerprotect:cluster-role-binding
- kubectl delete namespace powerprotect
Remove Velero components
Run the following commands to remove the Velero components:
- kubectl delete crd -l component=velero
- kubectl delete clusterrolebinding -l component=velero
- kubectl delete namespace velero-ppdm
Remove images from cluster nodes
Run the following commands to remove the Docker Hub images from the cluster nodes:
- On the worker nodes, run sudo docker image ls
- To remove any images that return powerprotect-cproxy, powerprotect-k8s-controller, powerprotect-velero-dd, or velero, run sudo docker image remove IMAGEID
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\