docs: gateway certificate issuance model - #307
Merged
Merged
Conversation
Document how a Gateway/HTTPProxy HTTPS hostname becomes an issued, served TLS certificate: ownership boundaries between NSO, cert-manager, the deployer, external-dns, and Envoy Gateway; the two issuance paths (hub-issue-and-propagate vs downstream member solve); issuer selection including the ClusterIssuer-vs-namespaced-Issuer kind distinction that hid infra#3410; the upstream to downstream projection; the HTTP-01 solver path; config reference; automatic re-issuance; and operator-generic failure modes. Complements the alert-focused runbook rather than replacing it, and cross -links both ways. Key changes: - Add docs/gateway-certificate-issuance-model.md - Link the model doc from docs/runbooks/gateway-tls-certificates.md
ecv
marked this pull request as ready for review
July 27, 2026 19:27
ecv
enabled auto-merge
July 27, 2026 19:27
ecv
requested review from
0xmc,
JoseSzycho,
kevwilliams,
mattdjenkinson and
privateip
July 27, 2026 21:18
mattdjenkinson
approved these changes
Jul 30, 2026
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.
Adds a doc explaining how a Gateway/HTTPProxy HTTPS hostname becomes a working TLS certificate: who owns which step, the two issuance paths, how the issuer is picked, and how it re-issues and fails.
Written to make one class of bug legible — an operator reading it can tell a wiring mistake from expected behaviour. That distinction is exactly what let infra#3410 hide for months.
Complements the alerts runbook rather than replacing it; the two cross-link.
Docs-only. Closes #269.
Note
One claim to confirm against the deployed setup: the doc says NSO issues against a
ClusterIssuerand treats a per-gateway namespacedIssueras deployment wiring its solver ignores. Please sanity-check that matches reality.