K8s: OSS Cluster API limitation #1670
Merged
Conversation
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
kaitlynmichael
requested review from
heinrich-redislabs,
shreyaverma-git and
a team
andy-stark-redis
approved these changes
Jun 5, 2025
Co-authored-by: andy-stark-redis <[email protected]>
heinrich-redislabs
approved these changes
Jun 9, 2025
|
|
||
| ## `ingressOrRouteSpec` for Active-Active databases | ||
|
|
||
| Versions 6.4.2 or later of Redis Enterprise for Kubernetes include a feature for ingress configuration. The `ingressOrRouteSpec` field is available in the RedisEnterpriseCluster spec to automatically create an Ingress (or route) for the API service and databases (REAADB) on that REC. See [REC external routing]({{< relref "/operate/kubernetes/networking/ingressorroutespec" >}}) for more details. | ||
|
|
||
| This feature only supports automatic Ingress creation for Active-Active databases created and managed with the RedisEnterpriseActiveActiveDatabase (REAADB) custom resource. Use with the standard Redis Enterprise database (REDB) is not currently supported. | ||
|
|
||
| ## OSS Cluster API limitations | ||
|
|
||
| When using [OSS Cluster API]({{< relref "/operate/rs/databases/configure/oss-cluster-api" >}}) with Redis Enterprise for Kubernetes, clients must specify the IP addresses of Redis instances to perform operations. Since Pod IP addresses are internal to the Kubernetes cluster and not publicly accessible, **OSS Cluster API can only be used by clients running on pods within the same Kubernetes cluster as the Redis Enterprise pods.** Using OSS Cluster API from outside the Kubernetes cluster is not tested and currently not supported. |
There was a problem hiding this comment.
The with Redis Enterprise for Kubernetes is not really necessary, because the limitation holds for k8s/non-k8s deployments.
kaitlynmichael
commented
Jun 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
DOC-5101