We have two etcd clusters running in Kubernetes one act as primary(A
) and the second one act as backup(B
). We also have etcdctl make-mirror
in place between these two clusters, now the problem is if we switch traffic from cluster A
to B
then cluster B
becomes primary, and cluster A
becomes the backup cluster. There is an F5
load balancer in front of these two clusters.
I'm looking for a mechanism/trigger that will detect this traffic change and trigger the pipeline which then spins up the replication pod on cluster B
and take down the replication pod on the cluster A
side.
I'm also open to suggestions about this workflow is there any better way we can achieve two-way replication for etcd? am I missing something?