Support for cross-K8s-cluster replication for RedisReplication deployment type: added ExternalMaster configuration#1771
Open
sergmour wants to merge 1 commit into
Open
Conversation
sergmour
requested review from
drivebyer,
iamabhishek-dubey and
shubham-cmyk
as code owners
sergmour
force-pushed
the
external-master
branch
2 times, most recently
from
ec58ed9 to
ceffc0c
Compare
Signed-off-by: Sergei Mouravyov <sergei.mouravyov@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a cross-K8s-cluster replication feature to RedisReplication deployment type. This functionality is essential for enterprise-type deployments as cross-region replication is a requirement, and K8s-clusters cannot span between regions and cloud providers.
The PR adds a slave-only mode to a RedisReplication deployment. In this mode all Redis servers are deployed as slaves connecting and replicating from the configured ExternalMaster. ExternalMaster is normally a host:port endpoint residing in a separate (primary) K8s cluster exposed by a LoadBalancer or NodePort.
A typical multi-K8s-cluster RedisReplication deployment would contain a primary RedisReplication deployment with 1 master, 2 slaves and 3 sentinels. Secondary (slave-only) deployments in other K8s clusters will contain just 3 slaves replicating from the primary master exposed by an LB or a NodePort. Below is a typical diagram:
The changes affect the following areas:
Imlements issue #1772 - [Feature] Support cross-K8s-cluster replication for RedisReplication deployment type - add External-Master configuration
Type of change
Checklist
Additional Context