You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Run the Tenant RGD local pilot: adoption rehearsal + parity diff on the Docker clusterΒ #2487
Part of #1932 β step 3b, the live exercise of the pilot scaffolding #2389 shipped. Gates Phase B of the ownership-transition design (ADR on the epic, 2026-07-05).
Problem
The Tenant RGD (#2197) has never been instantiated β no cluster has ever expanded a Tenant CR. Before the prod swap we need proof of (a) parity: the RGD's 10 expanded objects match the hand-written skeleton, and (b) adoption: kro v0.9.2 silently takes over pre-existing Flux-created objects via forced SSA (verified in source; needs live confirmation).
Proposal (one local-cluster session)
Bring up the Docker-provider cluster; enable the opt-in tenant-ascoachingogvaner.yaml in k8s/providers/docker/apps/kustomization.yaml.
Parity: diff the kro-expanded objects against the skeleton manifests (normalize managed-fields/labels).
Adoption rehearsal (the exact prod sequence): reset, apply the 10 skeleton objects first, then enable the Tenant CR β verify silent takeover (kro.run/applyset field manager, ApplySet labels), zero deletes/recreates.
The platform AGENTS.md maintenance rules bar agent runs from starting clusters ("Never run a cluster"), so this needs either a maintainer-attended/sanctioned session or an explicit exception for this one-off pilot β flagging rather than self-granting. GHCR creds must be seeded in the local OpenBao (infrastructure/ghcr/auth) for the OCIRepository leg; the expansion itself validates without them.
#2319 - feat(security): cosign-verify the infrastructure Flux OCI artifact [closed] #2339 - docs(agents): record merge-queue mechanics + root-cause-before-requeue [closed]
π Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
π§ͺ Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
π¬ Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Jul 5, 2026
π Related PRs
#2319 - feat(security): cosign-verify the infrastructure Flux OCI artifact [closed]
#2339 - docs(agents): record merge-queue mechanics + root-cause-before-requeue [closed]
π Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.π§ͺ Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:π¬ Have feedback or questions? Drop into our discord!