K8s: OSS Cluster API - Babylon release feature#2635
Merged
kaitlynmichael merged 12 commits intorelease-k8s-babylonfrom Feb 2, 2026
Merged
K8s: OSS Cluster API - Babylon release feature#2635kaitlynmichael merged 12 commits intorelease-k8s-babylonfrom
kaitlynmichael merged 12 commits intorelease-k8s-babylonfrom
Conversation
Contributor
Contributor
dwdougherty
requested changes
Jan 13, 2026
Collaborator
dwdougherty
left a comment
dwdougherty
left a comment
There was a problem hiding this comment.
Just a couple of comments: one typo and one sentence that probably needs to be rewritten.
Co-authored-by: David Dougherty <david.dougherty@redis.com>
Co-authored-by: David Dougherty <david.dougherty@redis.com>
dwdougherty
approved these changes
Jan 13, 2026
Collaborator
dwdougherty
left a comment
dwdougherty
left a comment
There was a problem hiding this comment.
LGTM, @kaitlynmichael. Approved.
| 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 | ||
| ## OSS Cluster API support |
There was a problem hiding this comment.
That's actually so heartwarming - instead of limitations, we are explaining the new capabilities.
|
The more I think about it, the more I'm convinced that we should stress the fact that the consequence of enabling external access for OSS cluster is having a load balancer for every pod running a redis enterprise node. Load balancers are important resources that cost money. Provisioning extra load balancers should not be a surprise. |
|
There is another requirement/limitation that needs to be mentioned regarding OSS clsuter with external access. It may or may not be obvious, but users may not create OSS clusters with external access using Redis Enterprise REST API directly. They must do it using the RedisEnterpriseDatabase object. While the limitation may be obvious, it should be mentioned. |
heinrich-redislabs
approved these changes
Jan 20, 2026
# Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
kaitlynmichael
added a commit
that referenced
this pull request
Feb 10, 2026
* vanilla-k8s supported distro * openshift support * eks * aks * gke * RKe2 * tkgi * vks * release notes * release notes * typo fix * K8s: OSS Cluster API - Babylon release feature (#2635) * page structure and intro * update RS page * cluster-aware-clients page * update limitations * Update content/operate/kubernetes/networking/cluster-aware-clients.md Co-authored-by: David Dougherty <david.dougherty@redis.com> * Update content/operate/kubernetes/networking/cluster-aware-clients.md Co-authored-by: David Dougherty <david.dougherty@redis.com> * add vs specify clarification * specify LB services are created * note about LB being resource heavy * add limitations * change annotations wording --------- Co-authored-by: David Dougherty <david.dougherty@redis.com> * update version and date * new RS version, API changes * K8s: credential changes for Babylon release (#2695) * RED-180515 changes * change cluster cred secret * corrections * removed change REC secret * Add examples for fuzzy search on specific attributes (#2689) * Add examples for fuzzy search on specific attributes Clarify that fuzzy search terms should NOT be wrapped in quotes when targeting a specific field. Using quotes (e.g., @field:("%word%")) converts the query to an exact phrase search instead of a fuzzy search. Added: - New subsection 'Fuzzy search on a specific attribute' - Correct syntax: @field:(%word%) using parentheses without quotes - Warning alert explaining the quotes pitfall - Examples for single field fuzzy search with distance 1 and 2 - Example combining fuzzy searches on multiple fields with OR * Copy edits --------- Co-authored-by: David W. Dougherty <dwdougherty@gmail.com> * DOC-6225 add underscore to embeds folder to prevent publication * Revert "DOC-6225 add underscore to embeds folder to prevent publication" This reverts commit ae5fe41. * DOC-6225 added _index.md to prevent publishing embeds * DEV: add missing field definitions to CLIENT LIST page (#2735) * DEV: add missing field definitions to CLIENT LIST page * Punctuation * flex limitations - RQE, TS, AA (#2728) * flex limitations - RQE, TS, AA * Fix formatting of unsupported features list * Update for redisvl 0.9.1 * Update for redisvl 0.7.0 * DOC-6231 updates for initial health checks * DOC-6231 moved failback config to its own section * DOC-6012 RS: Reverted DB version management changes for RS product lifecycle (#2742) * Fix hdel example in Python and Rust (#2739) * fix: Fix python hdel example * fix: Fix rust hdel example * DEV/OP/INT: add Redis uni links (#2743) * Update content/operate/rc/api/api-reference/openapi.json * Update rs-prometheus-metrics-v2.md (#2748) * Update rs-prometheus-metrics-v2.md update metric * Fixed typo --------- Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> * DEV: (cmds) update compat. info. (#2746) * DEV: (cmds) update compat. info. * Added CLUSTER SHARDS compat. info. * docs: replace unmaintained redlock-py with redlock-ng * DOC-6241 added k8s reloader note * DOC-6241 moved reloader example config * DOC-6241 removed unwanted comment following feedback * Clarify OSS Cluster API support availability * DOC-6236 added setup video link * Clarified ordering guarantees in XREADGROUP (#2752) Clarified ordering guarantees for CLAIM in XREADGROUP documentation. * K8s: unicorn maint 8 RN (#2754) * unicorn maint 8 * fix weights --------- Co-authored-by: David Dougherty <david.dougherty@redis.com> Co-authored-by: Jeremy Plichta <jeremy.plichta@redis.com> Co-authored-by: David W. Dougherty <dwdougherty@gmail.com> Co-authored-by: Andy Stark <andrew.stark@redis.com> Co-authored-by: Alon Magrafta <50071256+AlonMagrafta@users.noreply.github.com> Co-authored-by: redisdocsapp[bot] <177626021+redisdocsapp[bot]@users.noreply.github.com> Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> Co-authored-by: ok3721 <76622058+ok3721@users.noreply.github.com> Co-authored-by: Maayan Agranat <107346841+maayanagranat@users.noreply.github.com> Co-authored-by: Vivek Dagar <vivekdagar@zohomail.in> Co-authored-by: Igor Malinovskiy <u.glide@gmail.com> Co-authored-by: Lior Kogan <koganlior1@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
3 participants
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.
No description provided.