docs: 26.05_1 release — per-SNI ACME and multi-tenant TLS#3
Merged
Conversation
- Extend `configuration/listeners.md` SNI section with a new "Per-SNI ACME (Multi-tenant TLS)" subsection covering the 26.05_1 feature: independent ACME schedulers per SNI block, the cert-vs-acme mutual-exclusion rule, implicit hostname derivation from `acme.domains`, the global case-insensitive domain-uniqueness rule, and cold-start observability (the `zentinel_tls_sni_cert_skip_total` counter). - Add `examples/multi-tenant-tls.md` with a complete worked config for a SaaS use case (root ACME + tenant A HTTP-01 + tenant B Cloudflare DNS-01 wildcard + a manual cert), including operational notes on storage isolation, first-start behavior, and the metric to watch. - Snapshot the finalized top-level docs into `content/v/26.05/` so the version picker can serve a frozen 26.05 archive. - Update `config.toml` version picker: `current = "26.05"`, add 26.05 (latest) and 26.04 entries to the list. Drop the stale 26.03 entry that pointed at `/` — that URL now serves 26.05.
Deploying zentinelproxy-io-docs with
|
| Latest commit: |
a8e7d8d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://db245541.zentinelproxy-io-docs.pages.dev |
| Branch Preview URL: | https://docs-26-05-1-per-sni-acme.zentinelproxy-io-docs.pages.dev |
Three files were added to top-level docs after the v/26.04 snapshot was created and never backported: - agents/waf-engines.md (updated 2026-03-04) - concepts/agent-pipeline.md (updated 2026-03-02) - print.md All three predate the 26.04 release, so they belong in the 26.04 archive. Copy them in so /v/26.04/ matches top-level (modulo content that genuinely arrived later, like the new 26.05 multi-tenant-tls example).
2 tasks
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.
Summary
Documents the per-SNI ACME feature shipped in zentinel 26.05_1 and bumps the version picker so 26.05 is now Latest.
Changes
content/configuration/listeners.md— extends the SNI section with a "Per-SNI ACME (Multi-tenant TLS)" subsection covering:RenewalSchedulerpersni-certblock (Option B isolation).acme.domainsand the precedence order vs explicithostnamesandpriority-hostnames.zentinel_tls_sni_cert_skip_totalcounter, and the operator's "stuck issuance" signal.content/examples/multi-tenant-tls.md— new worked example: SaaS listener with root ACME + tenant A (HTTP-01) + tenant B (Cloudflare DNS-01 wildcard) + a manual partner certificate. Includes operational checklist.content/v/26.05/— snapshot of the finalized top-level docs as the frozen 26.05 archive.content/v/26.04/— backfill the three files that had drifted out of the 26.04 archive (agents/waf-engines.md,concepts/agent-pipeline.md,print.md). All three predate the 26.04 release per theirupdateddates and belong in that archive.config.toml— version picker updated:current = "26.05".label = "latest"pointing to/./v/26.04/./, which now serves 26.05).Notes
Marketing site (
zentinelproxy.io) intentionally not touched. The blog has been silent since 26.02; that's an editorial gap, not a docs gap.