Skip to content

K8s: Gateway API routing (eden release) - #4277

Open
kaitlynmichael wants to merge 1 commit into
release-k8s-edenfrom
DOC-7109
Open

kaitlynmichael wants to merge 1 commit into
release-k8s-edenfrom
DOC-7109

Conversation

@kaitlynmichael

@kaitlynmichael kaitlynmichael commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Documents Gateway API support in the Redis Software for Kubernetes operator (RED-112546). The operator attaches TLSRoute resources to a platform-owned Gateway to expose the cluster API, Cluster Manager UI, metrics, and Active-Active databases.

Hold: do not merge until the operator release that ships this feature is generally available. Jira: DOC-7109.

Changes

  • New page: networking/gateway-api.md
  • Cross-links and short additions on 11 existing pages in networking/, architecture/, active-active/, and re-clusters/
  • Link-text fix (ingressOrRoutes to ingressOrRouteSpec) on prepare-clusters.md and create-reaadb.md

The API reference pages are not edited here. The k8s_apis_sync workflow regenerates them from the release bundle.

Sources

Field names, defaults, status conditions, event reasons, and error messages come from the operator source and CRDs on the main branch. Example manifests and command output come from the feature's demo recordings. Migration steps follow the Phase 1 design doc's runbook.

For SME review

Please confirm these. Each one is inferred from the source rather than stated in it:

  1. Prerequisites: DNS records must resolve each exposed FQDN to the Gateway's address.
  2. Troubleshooting, RoutePending row: the remedy "check that gatewayRef names an existing Gateway and that your Gateway controller is running."
  3. Troubleshooting, "refusing to tear down the gateway route" row: the remedy "select the database for Gateway exposure again, or configure another exposure method on that cluster first."
  4. Expose Active-Active databases: "Each participating cluster needs its own fqdnSuffix." This comes from the design doc; no validation enforces it.
  5. Client test: the redis-cli example includes a client certificate and key, as in the demo. Is client authentication required, or only used in that environment?

Not covered, and open for input: TLS certificates. Clients that verify certificates will see the REC's certificate under the Gateway hostname. Both examples use an option that skips verification.

Generated with Claude Code


Note

Low Risk
Documentation-only changes with no runtime or API behavior in this repo; merge timing is tied to the operator GA release noted in the PR description.

Overview
Adds documentation for Gateway API routing in Redis Software for Kubernetes: a new networking/gateway-api.md page describing REC spec.gateway, operator-managed TLSRoute attachment to a customer-owned Gateway (TLS passthrough/SNI), exposure of cluster API/UI/metrics and Active-Active databases, status/troubleshooting, and migration from ingressOrRouteSpec without downtime.

Existing guides are updated to cross-link that page and call out Gateway-specific Active-Active steps (replicationPort on every RERC copy). Networking and architecture overviews now list Gateway API alongside ingress/Istio/routes. Two prerequisites pages fix the link text ingressOrRoutes → ingressOrRouteSpec.

Reviewed by Cursor Bugbot for commit 8c06256. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions

github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

DOC-7109

@github-actions

Copy link
Copy Markdown
Contributor

🧠 Redis Memory

Found 5 related items from repository history (5 new this commit):

Memory updated at 8c06256

@dwdougherty dwdougherty left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Language LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants