This article explains how customers who deploy SWIFT from the Google Cloud Marketplace can start a migration or DR Proof of Concept (POC) by syncing any Kubernetes cluster (EKS/AKS/OKE/on-prem) to a Google Kubernetes Engine (GKE) cluster.
Deploy the SWIFT from GCP-Marketplace.
POC Usecase
Migration POC
1. As mentioned in KB point #13, make sure you deploy the templates based on your specific use case.
2. You can also refer to KB point #14, which explains how to add the cluster into SWIFT and configure the replication settings. This guide includes steps for registering both source and target clusters.
3. Additionally, you can create a DR Policy to enable frequent syncs using Passthrough Sync. Refer to the KB on applying a DR Policy for Passthrough Sync during an Any-to-GKE migration. This policy ensures continuous and incremental updates to your GKE target during the POC.
DR POC
Pre-requisite
1. At least source cluster should be added
2. For Stage sync, there should be storage pool added.
Lets perform DR POC as below.
1. Once added the cluster, then you can do Stage1 and Stage2 sync
2. If you want to set up a DR Policy for stage sync, the refer this KB.
3. Also if you want to do failover and fallback, then refer this KB