-
Notifications
You must be signed in to change notification settings - Fork 70
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cluster relocation #1261
Comments
@sentaycan That is, you'll need to create a replicationdestination on the old source (new destination) cluster, and your new PVC on the destination (that you now want to be the source) should be the sourcePVC for a new replicationsource. |
One note - on the new destination cluster, since it contains the old Source PVC, you can use this as your destinationPVC in your replicationdestination if you wish - this means the initial sync back from new source to new destination should be quicker as the destination PVC already contains a lot of the data. |
Thank you, but I want to connect the PVC in DestinationCluster to my application, how can I do this, I couldn't do it :( |
And my question was actually this. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hello, I am copying my PVC to a cluster in a different region as below, but now I want to delete my source cluster and use my destination cluster as source cluster, what is the most optimal way to do this?
kubectl --context west2 -n mysql create -f - <<EOF apiVersion: volsync.backube/v1alpha1 kind: ReplicationDestination metadata: name: mysql spec: rsyncTLS: copyMethod: Snapshot capacity: 8Gi accessModes: ["ReadWriteOnce"] storageClassName: gp3-csi volumeSnapshotClassName: csi-aws-vsc keySecret: east-west serviceType: LoadBalancer EOF
kubectl --context east2 -n mysql create -f - <<EOF apiVersion: volsync.backube/v1alpha1 kind: ReplicationSource metadata: name: mysql spec: sourcePVC: data-mysql-0 trigger: schedule: "*/5 * * * *" rsyncTLS: keySecret: east-west address: abad73aa2ca4441ed8c9e13f1095c453-95258c1d3ff95327.elb.us-west-2.amazonaws.com copyMethod: Snapshot volumeSnapshotClassName: csi-aws-vsc EOF
The text was updated successfully, but these errors were encountered: