Secret Store: A secret store is configured on both clusters. This will store the credentials for the objectstore.
Objectstore: An AWS S3 compatible, AWS S3, GCP Object Storage, or Azure Blob Storage.
Network Connectivity:
Kubernetes: All worker nodes are able to reach Kubernetes API endpoints on both Kubernetes clusters, for example, port 6443, 443 and so on.
Portworx: Open port in the range of 9001-9020 for Portworx worker nodes to communicate with each other.
To know more about the specific ports for your environment, see the Network table on the Prerequisites page.
Default StorageClass: At most one StorageClass object is configured as the default. Having multiple default StorageClasses will cause PVC migrations to fail.
Cloud Environment: Depending on your cloud provider (EKS, GKE, AAD enabled AKS, or OKE) ensure that you have successfully applied the instructions provided on the respective page for setting up your destination cluster.
A separate Portworx cluster of same version is installed on both the source and destination clusters.
storkctl is installed on both clusters. Note that always use the latest storkctl binary tool by downloading it from the current running Stork container. See the Prepare your cluster page.
Applications Registration: For certain Kubernetes applications, you should create an ApplicationRegistration CR first to facilitate the successful migration of them. Refer to the ApplicationRegistrations page for more information.
Secret Store: A secret store is configured on both clusters. This will store the credentials for the objectstore.
Objectstore: An AWS S3 compatible, AWS S3, GCP Object Storage, or Azure Blob Storage.
Network Connectivity:
OpenShift4+: All worker nodes are able to reach Kubernetes API endpoints on both Kubernetes clusters, for example, port 6443, 443 and so on.
Portworx: Open port in the range of 17001-17020 for Portworx worker nodes to communicate with each other.
To know more about the specific ports for your environment, see the Network table on the Prerequisites page.
Default StorageClass: At most one StorageClass object is configured as the default. Having multiple default StorageClasses will cause PVC migrations to fail.
Cloud Environment: Depending on your cloud provider (EKS, GKE, AAD enabled AKS, or OKE) ensure that you have successfully applied the instructions provided on the respective page for setting up your destination cluster.
A separate Portworx cluster of same version is installed on both the source and destination clusters.
storkctl is installed on both clusters. Note that always use the latest storkctl binary tool by downloading it from the current running Stork container. See the Prepare your cluster page.
Applications Registration: For certain Kubernetes applications, you should create an ApplicationRegistration CR first to facilitate the successful migration of them. Refer to the ApplicationRegistrations page for more information.