Repository navigation
feat(business-site): move the tenant to the signed v3.10.0 release - #6394
Conversation
v3.10.0 repairs the refused v3.9.0 rollout: each migration container now sets runAsNonRoot itself, as Kyverno validate-pod-security requires (business-site#629). It brings the portal schema migration Job's first run and the daily retention CronJob (#620), both on the release's own image and the business-site-portal-db-migration Secret. It also carries the new public prices and launch offer (#625) and default-off portal features (#616, #622, #623, #626). The portal stays switched off. Prepared with scripts/bootstrap-tenant-source.sh --prepare-canonical-upgrade against the read-only production context, on top of the settled v3.9.0 binding (#6390). Same approved publisher revision; no new approval. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pinned CI render changes exactly one entry, Tenant flux-system/business-site, from 7ecffdd0… to 6aca6f32…. Only its source digest changes; no authorization resource is added or removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codex review |
Codex Review Summary: ✅ CompletedThis 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. |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
✅
|
✅
|

Why
Production has been refusing the business-site tenant since #6384 (v3.9.0). Kyverno
validate-pod-securityrefused the migration Job at dry-run, because the Job setrunAsNonRootonly at pod level. Nothing from v3.9.0 was applied; the site still serves v3.8.0 and the portal is off, butbusiness-site/business-siteis ReconciliationFailed.business-site v3.10.0 has the fix (devantler-tech/business-site#629): each container sets
runAsNonRootitself. I checked the published package (sha256:5d083252…) from the registry. The Job, the retention CronJob and the WebApp share imagesha256:128778d4…, and both containers setrunAsNonRoot: true.The release also carries:
The portal stays switched off.
What
The business-site Tenant moves to v3.10.0, signed by the same approved publisher revision, so it needs no new approval.
scripts/bootstrap-tenant-source.sh --prepare-canonical-upgradeagainst the read-only production context, on top of the settled v3.9.0 binding (chore(security): regenerate the approved publish-workflow revisions #6390).Authorization ledger approval. The pinned kubectl v1.36.2 / Kustomize v5.8.1 render in CI changes exactly one entry, Tenant flux-system/business-site, from
7ecffdd0e692d09d224ad21029ee515b6833a47bd821333cbd502476ade1a6dfto6aca6f326acea4f267e0e35f8a48ce091ca7610c9bf633f13e99280431d571d3. Only its source digest changes; no authorization resource is added or removed.After merge
The agent checks:
portal schema migration completed, and the ledger holds the release's 25 or more versions;Part of devantler-tech/business-site#302 and devantler-tech/monorepo#3939.
🤖 Generated with Claude Code