From b311a66ff83c272cb5e232ea010cd05aa11d14a6 Mon Sep 17 00:00:00 2001 From: JJGadgets Date: Thu, 23 May 2024 16:38:59 +0800 Subject: [PATCH] fix(flux): add prune disable patches I wonder how well those nested patches will work --- kube/clusters/sinon/flux/flux-repo.yaml | 32 ++++++++++++++++++++++++- 1 file changed, 31 insertions(+), 1 deletion(-) diff --git a/kube/clusters/sinon/flux/flux-repo.yaml b/kube/clusters/sinon/flux/flux-repo.yaml index c81e2029..9c9f3779 100644 --- a/kube/clusters/sinon/flux/flux-repo.yaml +++ b/kube/clusters/sinon/flux/flux-repo.yaml @@ -29,10 +29,11 @@ metadata: kustomization.flux.home.arpa/default: "false" wait.flux.home.arpa/disabled: "true" kustomization.flux.home.arpa/helmpatches: "false" + kustomization.flux.home.arpa/prunepatches: "false" spec: interval: 5m0s path: ./kube/clusters/sinon/flux - prune: false + prune: true wait: false sourceRef: kind: GitRepository @@ -57,6 +58,12 @@ spec: # name: sinon-versions # optional: false patches: + - patch: |- + - op: add + path: "/metadata/labels/kustomize.toolkit.fluxcd.io~1prune" + value: "disabled" + target: + kind: Namespace - patch: |- apiVersion: kustomize.toolkit.fluxcd.io/v1 kind: Kustomization @@ -218,6 +225,29 @@ spec: version: v1 kind: Kustomization labelSelector: wait.flux.home.arpa/disabled=true + - patch: |- + apiVersion: kustomize.toolkit.fluxcd.io/v1 + kind: Kustomization + metadata: + name: not-used + spec: + patches: + - patch: |- + - op: add + path: "/metadata/labels/kustomize.toolkit.fluxcd.io~1prune" + value: "disabled" + target: + kind: Namespace + - patch: |- + - op: add + path: "/metadata/labels/kustomize.toolkit.fluxcd.io~1prune" + value: "disabled" + target: + kind: PersistentVolumeClaim + target: + group: kustomize.toolkit.fluxcd.io + kind: Kustomization + labelSelector: kustomization.flux.home.arpa/prunepatches notin (false) - patch: |- apiVersion: kustomize.toolkit.fluxcd.io/v1 kind: Kustomization