Demo: rsync fail-back

[JohnStrunk]

Describe the feature you'd like to have. Our demos thus far showing failover have gone 1-way. We should have something that shows how to re-sync and re-activate the original primary.

What is the value to the end user? (why is it a priority?)

How will we know we have a good solution? (acceptance criteria)

Additional context

• This will require a second source/destination for the reverse direction, but if these are created independently, they will cause a full re-sync from the destination back to the source even though the majority of the data is already on the source cluster.
• We should be able to seed the re-sync w/ the "original" primary data to minimize copying.
• I'm not sure how much code will be needed here, but it's non-zero.

[cooktheryan]

The current plan for this is to modify the fields in the secret. Then create new replication source and destinations and define the specific keys to use.

[JohnStrunk]

/close

[openshift-ci[bot]]

@JohnStrunk: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.