Skip to content

Commit b71cca3

Browse files
committed
docs(unified-tls-pki): fix the anchor's delivery path and two citations
The tenant does not reach the trust anchor through a dashboard resource map. No converged engine grants it there, and mongodb's resource map carries the argument for why: a name grant conveys whatever occupies the name, where the label path conveys only what the platform vouched for. The sentence was target-tense at the merge base, describing a name nothing had shipped; repointing it at the object now in the tree turned it into a claim about shipped behaviour that the document's own RBAC reasoning contradicts. "Never shipped in a release" was the changelog's wording for the ExposureClass/ServiceExposure removal, and it reads as stronger than it is: the API was present in the v1.6.0 release candidates published before it was dropped. Gone before v1.6.0 is the precise claim. Decision 0001's Consequences say the enforced legs of the canonical name are the application name and the release prefix. The prefix leg is enforced only because cozystack/cozystack#3411 added the ^[a-z0-9-]*$ pattern to ApplicationDefinitionRelease.Prefix, and the record listed the two PRs that built the controller but not the one that made that sentence true. A record's header is the part kept in step with reality. Assisted-by: LLM
1 parent 606a4d0 commit b71cca3

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

‎design-proposals/unified-tls-pki/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This proposal is the umbrella design for the work tracked by epic `cozystack/coz
1818
- **Edge (PRs):** `cozystack/cozystack#2988` (ACME wildcard on the default ingress-nginx path), `cozystack/cozystack#2989` (the CA-only trust-anchor helper), and `cozystack/cozystack#2990` (propagate the operator wildcard to per-tenant termination points — the PR implementing issue `cozystack/cozystack#2820`).
1919
- **Workstreams (issues):** `cozystack/cozystack#2812` and `cozystack/cozystack#2400` (closed, edge wildcard); `cozystack/cozystack#2814` (converge per-app TLS and close the trust-anchor delivery gap — the first consumer of this contract); `cozystack/cozystack#2815` (external DB exposure via Gateway TLS-passthrough); `cozystack/cozystack#2816` (end-to-end TLS for databases); `cozystack/cozystack#2977` (opt-in east-west encryption). Throughout this document a `cozystack/cozystack#NNNN` reference is an issue unless called out as a PR.
2020
- **Per-engine TLS series (PRs):** `cozystack/cozystack#2729` (redis), `cozystack/cozystack#2692` (mongodb), `cozystack/cozystack#2683` (rabbitmq), `cozystack/cozystack#2682` (opensearch), `cozystack/cozystack#2680` (mariadb). Each carries one engine onto this contract, and each is meant to land against it rather than ahead of it — the failure mode they exist to avoid is handing a tenant a key-bearing Secret (see Security). Which of them have landed is tracked in `cozystack/cozystack#2814`, not here.
21-
- **Related (consumers of this contract):** `design-proposals/external-database-exposure` — the sibling proposal under the same epic; its end-to-end TLS story has external clients validate against the `<release>.tenant-ca` object defined here. The structured `expose` model carries an "external implies TLS" rule that likewise points clients at this trust anchor. It has not landed: the proposal (`cozystack/community#29`) was closed, and the `ExposureClass` / `ServiceExposure` implementation (`cozystack/cozystack#3081`) was removed again by `cozystack/cozystack#3218` in favour of a native `Service` `loadBalancerClass`, so it never shipped in a release. Both consume this proposal's output and define no PKI of their own.
21+
- **Related (consumers of this contract):** `design-proposals/external-database-exposure` — the sibling proposal under the same epic; its end-to-end TLS story has external clients validate against the `<release>.tenant-ca` object defined here. The structured `expose` model carries an "external implies TLS" rule that likewise points clients at this trust anchor. It has not landed: the proposal (`cozystack/community#29`) was closed, and the `ExposureClass` / `ServiceExposure` implementation (`cozystack/cozystack#3081`) was removed again by `cozystack/cozystack#3218` in favour of a native `Service` `loadBalancerClass`, so it was gone before `v1.6.0`. Both consume this proposal's output and define no PKI of their own.
2222

2323
All repository paths below refer to the `cozystack/cozystack` repository. A path belonging to an engine's TLS series is cited from that series' branch and named with it; everything else is cited from the platform. This document states the contract, not the state of a branch — [`design-proposals/README.md`](../README.md) is explicit that the codebase is the final source of truth for what the system does.
2424

@@ -219,7 +219,7 @@ What this *reuses* rather than rebuilds: Flux's release-name label and its nativ
219219

220220
## User-facing changes
221221

222-
A tenant sees one canonical, key-free trust-anchor object per managed application — `<release>.tenant-ca`, carrying only `ca.crt` — through the dashboard resource map and the `tenantsecrets` projection, in the same shape across every engine. An operator sees one interface to choose the edge certificate source. There is no new tenant-authored input.
222+
A tenant sees one canonical, key-free trust-anchor object per managed application — `<release>.tenant-ca`, carrying only `ca.crt` — through the `tenantsecrets` projection, in the same shape across every engine. It reaches the tenant by label rather than by name: no chart's dashboard resource map grants the anchor, because a name grant would convey whatever occupies that name, where the label path conveys only what the platform has vouched for. An operator sees one interface to choose the edge certificate source. There is no new tenant-authored input.
223223

224224
## Upgrade and rollback compatibility
225225

‎design-proposals/unified-tls-pki/decisions/0001-the-trust-anchor-is-declared-by-a-namespaced-sentinel.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
- **Deciders:** `@lexfrei, @lllamnyp`
77
- **Proposal:** [`../README.md`](../README.md)
88
- **Decided in:** the API-owner review on [`cozystack/cozystack#3299`](https://github.com/cozystack/cozystack/pull/3299), recorded in the proposal by [`cozystack/community#36`](https://github.com/cozystack/community/pull/36)
9-
- **Implemented in:** [`cozystack/cozystack#3407`](https://github.com/cozystack/cozystack/pull/3407) and [`cozystack/cozystack#3408`](https://github.com/cozystack/cozystack/pull/3408)
9+
- **Implemented in:** [`cozystack/cozystack#3407`](https://github.com/cozystack/cozystack/pull/3407), [`cozystack/cozystack#3408`](https://github.com/cozystack/cozystack/pull/3408), and [`cozystack/cozystack#3411`](https://github.com/cozystack/cozystack/pull/3411), which added the release-prefix pattern the Consequences below rely on
1010

1111
## Context
1212

0 commit comments

Comments
 (0)