Repository navigation
K8s: Gateway API routing (eden release) - #4277
Open
kaitlynmichael wants to merge 1 commit into
Open
kaitlynmichael wants to merge 1 commit into
kaitlynmichael wants to merge 1 commit into
Conversation
Contributor
Contributor
Contributor
🧠 Redis MemoryFound 5 related items from repository history (5 new this commit):
Memory updated at 8c06256 |
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
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.
Summary
Documents Gateway API support in the Redis Software for Kubernetes operator (RED-112546). The operator attaches
TLSRouteresources 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
networking/gateway-api.mdnetworking/,architecture/,active-active/, andre-clusters/ingressOrRoutestoingressOrRouteSpec) onprepare-clusters.mdandcreate-reaadb.mdThe API reference pages are not edited here. The
k8s_apis_syncworkflow 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:
RoutePendingrow: the remedy "check thatgatewayRefnames an existing Gateway and that your Gateway controller is running."fqdnSuffix." This comes from the design doc; no validation enforces it.redis-cliexample 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.mdpage describing RECspec.gateway, operator-managedTLSRouteattachment to a customer-owned Gateway (TLS passthrough/SNI), exposure of cluster API/UI/metrics and Active-Active databases, status/troubleshooting, and migration fromingressOrRouteSpecwithout downtime.Existing guides are updated to cross-link that page and call out Gateway-specific Active-Active steps (
replicationPorton every RERC copy). Networking and architecture overviews now list Gateway API alongside ingress/Istio/routes. Two prerequisites pages fix the link textingressOrRoutes→ingressOrRouteSpec.Reviewed by Cursor Bugbot for commit 8c06256. Bugbot is set up for automated code reviews on this repo. Configure here.