[docs] Gateway API TLS and FQDN auto-discovery for Kubernetes deployment - #782
Closed
aspire-repo-bot[bot] wants to merge 2 commits into
Closed
Conversation
aspire-repo-bot
Bot
added
the
docs-from-code
… deployment Documents the new FQDN auto-discovery behavior introduced in microsoft/aspire#16551. When WithTls() is called without WithHostname(), a tls-fqdn-discovery pipeline step discovers the controller-assigned FQDN after Helm deploy and patches the Gateway listener hostname automatically. Also documents basic Gateway usage and the known-hostname TLS pattern for completeness. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
David Pine (IEvangelist)
force-pushed
the
docs/aspire-16551-gateway-tls-fqdn-discovery-5ce08194c3927301
branch
from
April 30, 2026 14:00
796bea3 to
f81026e
Compare
David Pine (IEvangelist)
marked this pull request as ready for review
April 30, 2026 15:21
Co-authored-by: David Pine <david.pine@microsoft.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
2 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.
Documents changes from microsoft/aspire#16551.
@mitchdennyTarget branch:
main— falling back tomainbecauserelease/13.4(resolved from the PR milestone13.4) does not yet exist onmicrosoft/aspire.dev.Why this PR is needed
PR microsoft/aspire#16551 adds support for Kubernetes Gateway API TLS configuration without a pre-known hostname. When
WithTls()is called withoutWithHostname(), a newtls-fqdn-discoverypipeline step automatically discovers the FQDN assigned by the gateway controller (e.g., Azure AGC), patches the listener, and bootstraps TLS — enabling single-deploy TLS for controllers that assign FQDNs dynamically.The existing
deployment/kubernetes.mdxpage had no documentation for the Gateway API, routing, or TLS at all. This is a significant user-facing feature gap.What was changed
Updated
src/frontend/src/content/docs/deployment/kubernetes.mdxwith a new "Configure Gateway API and TLS" section covering:AddGateway,WithGatewayClass,WithRoute(C# and TypeScript examples)WithHostname+WithTlspatternWithTls()withoutWithHostname(), including an explanation of thetls-fqdn-discoverypipeline step sequence and its 5-minute polling behaviorFiles modified
src/frontend/src/content/docs/deployment/kubernetes.mdx(updated — new section added)This draft PR needs human review before merging.