Skip to content

feat: add HTTPS support via Gateway sectionName#70

Closed
bdchatham wants to merge 2 commits intomainfrom
feat/https-gateway-section-name-v2
Closed

feat: add HTTPS support via Gateway sectionName#70
bdchatham wants to merge 2 commits intomainfrom
feat/https-gateway-section-name-v2

Conversation

@bdchatham
Copy link
Copy Markdown
Collaborator

Summary

Add SEI_GATEWAY_SECTION_NAME optional platform env var to target a specific Gateway listener (e.g., "https") in HTTPRoute parentRefs.

Rebased on the listener-model refactor (#69). The old PR (#68) had conflicts — this is a clean reimplementation on top of the current code.

Changes

  • internal/platform/platform.go — add GatewaySectionName (optional, not in Validate())
  • cmd/main.go — read SEI_GATEWAY_SECTION_NAME, wire to reconciler
  • internal/controller/nodedeployment/controller.go — add field to reconciler
  • internal/controller/nodedeployment/networking.go — pass sectionName to generateHTTPRoute, conditionally include in parentRef
  • Tests: sectionName included when set, omitted when empty

Supersedes #68.

Test plan

  • make test passes
  • make lint passes (0 issues)

🤖 Generated with Claude Code

Add SEI_GATEWAY_SECTION_NAME optional platform env var. When set,
all HTTPRoute parentRefs include sectionName (e.g., "https") to
target a specific Gateway listener for TLS termination.

Rebased on the listener-model refactor — sectionName flows through
the same generateHTTPRoute path as gatewayName/gatewayNamespace.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
GatewayName: os.Getenv("SEI_GATEWAY_NAME"),
GatewayNamespace: os.Getenv("SEI_GATEWAY_NAMESPACE"),
GatewayDomain: os.Getenv("SEI_GATEWAY_DOMAIN"),
GatewaySectionName: os.Getenv("SEI_GATEWAY_SECTION_NAME"),
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Can we make this required?

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@bdchatham
Copy link
Copy Markdown
Collaborator Author

Superseded by the multi-listener Gateway topology in #69 + #71. sectionName is unnecessary when per-protocol listeners use hostname matching for route attachment.

@bdchatham bdchatham closed this Apr 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant