[docs] Kubernetes Gateway TLS and FQDN auto-discovery - #799
Closed
aspire-repo-bot[bot] wants to merge 1 commit into
Closed
[docs] Kubernetes Gateway TLS and FQDN auto-discovery#799aspire-repo-bot[bot] wants to merge 1 commit into
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
aspire-repo-bot
Bot
added
the
docs-from-code
Documents the new FQDN discovery capability introduced in microsoft/aspire#16585 (backport of #16551 to release/13.3). - Explains WithTls + WithHostname for known-hostname TLS - Explains WithTls without WithHostname for FQDN auto-discovery - Describes the four-step auto-discovery flow (deploy, wait, patch, cert) - Documents WithTls() overload for auto-generated secret names - Adds a note about requirements (cert-manager, HTTP-01 solver) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
David Pine (IEvangelist)
force-pushed
the
docs/kubernetes-tls-fqdn-discovery-dabe71f1e8af58e4
branch
from
May 4, 2026 14:26
fbeb687 to
7994623
Compare
David Pine (IEvangelist)
marked this pull request as ready for review
May 4, 2026 18:02
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
1 participant
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#16585
Author:
@aspire-repo-bot[bot] (backport of changes from@mitchdenny)Targeting
main— falling back tomainbecauserelease/13.3does not exist onmicrosoft/aspire.dev. The source PR milestone is13.3.Why this PR is needed
microsoft/aspire#16585 adds support for using
WithTls(...)on a Kubernetes Gateway without callingWithHostname(...)first. Previously, TLS configuration required a known hostname upfront. Now,aspire deployautomatically discovers the hostname that the Gateway controller assigns after deployment (FQDN discovery), then patches the Gateway listener and HTTPRoutes so that cert-manager can issue a certificate using the HTTP-01 ACME solver.The existing
deployment/kubernetes.mdxhad no documentation on Gateway TLS configuration at all. This PR adds a dedicated Configure Gateway TLS section covering all threeWithTlspatterns.Summary of changes
Updated pages
src/frontend/src/content/docs/deployment/kubernetes.mdx— added a new "Configure Gateway TLS" section with:WithHostname+WithTls)WithTlsonly, noWithHostname) — the new behavior from this PRWithTls()with no arguments)Files modified
src/frontend/src/content/docs/deployment/kubernetes.mdx(updated — 124 lines added)