Skip to content

feat(tenants): prune-protect the ascoachingogvaner skeleton for the KRO handover #2488

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
devantler wants to merge 2 commits into
base: main
Choose a base branch
from
+10 −0
Draft

feat(tenants): prune-protect the ascoachingogvaner skeleton for the KRO handover #2488

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7f23124
feat(tenants): prune-protect the ascoachingogvaner skeleton for the K…
devantler Jul 5, 2026
2b66aa1
refactor(tenants): apply prune-protection via commonAnnotations
devantler Jul 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions k8s/bases/apps/ascoachingogvaner/kustomization.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,16 @@
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
# Phase A of the skeleton->Tenant-CR handover (#1932/#2486): when the KRO swap
# de-inventories these objects from the `apps` Kustomization, Flux must NOT
# garbage-collect them — kro adopts them in place (the tenant namespace holds
# the live database; the tenant Kustomization's finalizer would GC the whole
# app). Applied once here rather than per file so it also covers any object
# added to the skeleton before Phase B; none of these resources carries a pod
# template, so the annotation propagates to top-level metadata only. The whole
# directory is deleted at Phase B.
commonAnnotations:
kustomize.toolkit.fluxcd.io/prune: disabled
resources:
# external-dns-rbac stays platform-side: it grants the tenant's external-dns
# SA privileged cross-namespace reads (the kube-system Gateway, cluster-wide
Expand Down