Repository navigation
feat(gateway): serve devantler.tech, www and portal for business-site - #6188
Conversation
Turn on the business-site Tenant's own application and WebApp at the
already-verified v3.0.0 package. The platform-owned staging hold still
denies gateway traffic, so the site is not reachable yet.
- Admit exactly business-site.platform.devantler.tech for HTTPRoutes in
the business-site namespace; the catch-all denied every route there.
- Admit a tenant egress rule that is exactly {}: Cilium allows nothing
through it, and the package uses it to select egress default deny.
- Let the canonical source guard accept the source-only bootstrap shape
or both switches on together, never a half-enabled Tenant.
- Approve the moved Tenant ledger line and static-scan instance hash.
Part of #5247.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The ownership-label replay pins each tenant family's exact Kyverno counts. The business-site route fixtures add one admitted and four refused routes, and the empty-egress fixture adds one admitted policy. Part of #5247. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The business-site package now routes its public pages on devantler.tech and www, and its portal on portal.devantler.tech. The shared Gateway had no listener or certificate for those names, and the route allow-list admitted only the staging name. - A platform-applied Certificate in the business-site namespace covers all three names through the shared Cloudflare ClusterIssuer, like world-at-ruin's zone-trial certificate. - A ReferenceGrant lets the Gateway read only that Secret. - Three HTTPS listeners, named for the sections the package's routes attach to, terminate TLS with it. - restrict-tenant-route-hostnames admits the three names beside the staging name; fixtures cover both new routes, an unlisted subdomain and a *.devantler.tech wildcard. The apex and www keep their GitHub Pages records until the cutover, since external-dns never overwrites a record it does not own. Part of #6177 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… builds on its settled binding Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v3.2.1 is the first business-site release with the two-host runtime and the package-owned public and portal routes. It is signed by the approved publish-app revision d8b5d0e9, as v3.0.0 was. - The binding and the Tenant digest are the unedited output of `bootstrap-tenant-source.sh --prepare-canonical-upgrade --tag v3.2.1`, run against the settled v3.0.0 binding from #6197 and a read-only production context. The preparation verified the release (cosign, tag v3.2.1, source 16cf60a0, run 43400872692) and the live v3.0.0 source (Ready, generation 3). - The Tenant keeps #6174's enabled flags; only its digest moves to sha256:eec71bcf…c66e4. - The rendered authorization surface and the static-scan baseline move only the business-site Tenant entry. Part of #6177 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Authorization ledger approval (0ccd870)
Evidence: the only change to this rendered entry is Locally at this head: the Kyverno route-hostname tests pass (26/26), and these tests pass: |
@coderabbitai review |
Action not completed
|
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 52 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…the image check trusts v3.0.0 and v3.2.1 were signed by publish-app v19.0.12, which the tenant source approved but production's image admission check does not, so the staging Deployment was denied. v3.2.2 is signed by v19.0.5, which the admission check, the node pull rule and the tenant source all trust. Business-site's approvals become v19.0.12 (the binding it moves from) and v19.0.5 (the one it moves to); v8.0.0 is no longer used by it. The upgrade record, Tenant digest and publisher, scan-baseline hash and ledger line come from the platform's own preparation and validators. Part of #6177 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai review |
Action not completed
|
✅
|
✅
|
@codex review |
bugbot run |
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
The approvals library drops a consumer's first row once its publisher move lands, so the revision being moved from (v19.0.12) goes first and the destination (v19.0.5) second. Part of #6177 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> # Conflicts: # scripts/canonical-tenant-source-bindings.json
@coderabbitai review |
Action not completed
|
devantler
left a comment
There was a problem hiding this comment.
🤖 Generated by the Agentic Engineer
Self-review (fallback — CodeRabbit, Codex and Cursor Bugbot unavailable)
Reviewed commit: 49b46de
- CodeRabbit: rate limited at 2026-11-13T15:13:53Z ("Review limit reached", next included review in 52 minutes); also at 14:06:58Z
- Codex: usage limit at 2026-11-13T14:28:31Z ("You have reached your Codex usage limits for code reviews")
- Cursor Bugbot: no reaction, check run or comment 45 minutes after "bugbot run" at 2026-11-13T14:28:15Z; its last platform reply (#6151, 2026-11-12T22:20:56Z) was "GitHub account mismatch"
Verdict: 2 findings (P0: 0, P1: 0)

Why
The business site will serve its public pages on devantler.tech, and its portal on the portal subdomain, from the platform. The platform has no certificate or gateway entry for those names, and the staging app it now runs cannot start, because production's image check does not trust the release workflow revision that signed it.
What
The platform issues one certificate for the apex, its www name and the portal subdomain, opens a gateway entry for each, and lets the business site's routes use exactly those names. It moves the business site to a new signed release from the workflow revision the image check already trusts, and approves that revision for this tenant in place of one it no longer uses; the apex and www keep pointing at GitHub Pages, and the staging hold is lifted in its own change.
Part of #6177