Asynchronous DR supported Kubernetes resources in Tanzu

Asynchronous DR supports the following Kubernetes resources:

• PersistentVolumeClaim
• PersistentVolume
• Deployment
• DeploymentConfig
• StatefulSet
• ConfigMap
• Service
• Secret
• DaemonSet
• ServiceAccount
• Role
• RoleBinding
• ClusterRole
• ClusterRoleBinding
• ImageStream
• Ingress
• Route
• Template
• CronJob
• ResourceQuota
• ReplicaSet
• LimitRange
• PodDisruptionBudget
• NetworkPolicy

note

By default, Stork skips migrating NetworkPolicies which have CIDR set. To migrate NetworkPolicies which have CIDR set, use the skipNetworkPolicyCheck: true flag in the migration object.

Asynchronous DR does not support migration of Kubernetes custom resources that belong to specific groups. These groups are specified by the group value in the Custom Resource Definition (CRD). Groups listed here are not supported for migration by Asynchronous DR:

• autopilot.libopenstorage.org
• core.libopenstorage.org
• volumesnapshot.external-storage.k8s.io
• stork.libopenstorage.org
• kdmp.portworx.com

In other words, if you have custom resources defined under any of these groups, Asynchronous DR will not be able to handle or move these resources during a disaster recovery operation.

Follow the Application Registration document to know the supported custom resource definitions (CRDs) for asynchronous DR. The document also provides steps for registering a new CRD if it is not already listed.