When we deploy IRIS cluster using IKO, can we add async IRIS instance outside of the cluster?
Hello, we deploy IRIScluster using IKO on Red Hat OpenShift deployed in AWS. For DR, we have another AWS region on stand by. We do daily backups. I run a standalone IRIS in the second region. I want to add it as async member to the mirror to have some essential data available in the standby region. Is this possible?
Comments
You can try to use merge.cpf to define async member as part of the mirror
See "Deploy the Mirror Using Separate Merge Files"
My concern is that IKO deploys failover members with cluster local network addresses. Can an async that is located outside of the Kubernetes cluster be added to the mirror configured by IKO?
I don't know the reasons for this not to work, given that there is a network connectivity between mirror nodes in the cluster and async member. I did not try this myself
I appreciate the responses from Alexander Koblov. I wonder if @Bob Kuszewski could provide suggestion how is it possible to add mirror member outside of Kubernetes cluster.
It's possible to do, but it gets really tricky with the current version of IRIS and IKO. The networking piece alone is very complex.
If you can, my advice is to wait for this to be added as an official feature of IRIS & IKO. The design that we've been working through involves making services in each cluster so that all the mirror members can see each other, which is a far simpler design than what you need to do today.