🤖 Generated by the Daily AI Assistant
Part of #1932 — Phase A of the ownership-transition design (ADR on the epic, 2026-07-05).
Problem
The skeleton→Tenant-CR swap removes the 10 skeleton objects from the apps Flux Kustomization's inventory, and kustomize-controller deletes de-inventoried objects. For the tenant Namespace (holds the CNPG database) and the tenant's Flux Kustomization (kustomize-controller finalizer GCs the whole app), delete-then-recreate is data loss, not churn.
Proposal
Annotate all 10 objects under k8s/bases/apps/ascoachingogvaner/ with kustomize.toolkit.fluxcd.io/prune: disabled. Behavior-preserving today; makes the later inventory removal a no-op and protects against accidental skeleton deletion meanwhile.
Acceptance criteria
- All 10 skeleton objects carry the annotation; both overlays still build; validate passes.
- Merged and reconciled on prod before Phase B (the swap) starts.
Part of #1932 — Phase A of the ownership-transition design (ADR on the epic, 2026-07-05).
Problem
The skeleton→Tenant-CR swap removes the 10 skeleton objects from the
appsFlux Kustomization's inventory, and kustomize-controller deletes de-inventoried objects. For the tenant Namespace (holds the CNPG database) and the tenant's Flux Kustomization (kustomize-controller finalizer GCs the whole app), delete-then-recreate is data loss, not churn.Proposal
Annotate all 10 objects under
k8s/bases/apps/ascoachingogvaner/withkustomize.toolkit.fluxcd.io/prune: disabled. Behavior-preserving today; makes the later inventory removal a no-op and protects against accidental skeleton deletion meanwhile.Acceptance criteria