docs: expose Redpanda Console through Gateway API HTTPRoute (26.2)#1825
docs: expose Redpanda Console through Gateway API HTTPRoute (26.2)#1825david-yu wants to merge 1 commit into
Conversation
Add an 'Expose Redpanda Console with the Gateway API' section to the Console Kubernetes deploy page (operator PR #1329): Gateway API CRD + controller + Gateway prerequisites, Operator CRD and Helm tabs for the gateway block, route verification (Accepted/ResolvedRefs, allowedRoutes gotcha), and switching between Ingress and Gateway API. Both Ingress callouts now point at the new section, and the operator v26.2.x what's-new gains an entry. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Documents Gateway API HTTPRoute support for Redpanda Console (redpanda-operator#1329, merged 2026-06-30, ships in operator/chart v26.2.x).
Changes
Expose Redpanda Console with the Gateway APIondeploy:console/kubernetes/deploy.adoc:ingress and gateway cannot both be enabled; use one or the other)allowedRoutes.namespaces(the field that silently blocks cross-namespace route attachment when missed)spec.gateway) and Helm (gatewayvalues) tabs with callouts forparentRefs/sectionName,hostnames,pathTypeAccepted/ResolvedRefsroute conditions, theNotAllowedByListenersfailure mode, Gateway address lookup, and a pre-DNScurl --resolvecheckGateway API support for Redpanda Consoleentry under Redpanda Operator v26.2.x inget-started:release-notes/operator.adoc.Verification
Field names and behavior verified against operator
main: Console CRDspec.gateway(GatewayConfig:enabled,annotations,parentRefs[{name,namespace,sectionName}],hostnames,path,pathType) and the console chartgatewayvalues block, including the "HTTPRoute renders but attaches to nothing without parentRefs" default noted in values.yaml. Note the eng PR body's CR example usesspec.clusterSource; the actual CRD json field isspec.cluster, and the docs follow the code. The feature's changelog entries carry no beta marker, so the section is not badged beta (unlike the TLSRoute guide for Redpanda listeners).Preview pages
🤖 Generated with Claude Code