Open tropnikovvl opened 5 months ago
There is no way to ignore fields, you can only tell Flux to apply these objects as one-off:
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
spec:
patches:
- patch: |
- op: add
path: /metadata/annotations/kustomize.toolkit.fluxcd.io~1ssa
value: IfNotPresent
target:
kind: CustomResourceDefinition
name: (clustersecretstores.external-secrets.io|secretstores.external-secrets.io)
@stefanprodan Thanks for the answer!
How then will the update process occur when changing the version? Will it even work?
There is no update unless you remove the annotation from Git and cluster. I suggest using a HelmRelease for the external-secrets operator, as helm-controller doesn't correct drift by default and bundles will stay put.
We do haven an issue for implementing fields ignore here https://github.com/fluxcd/pkg/issues/696. It may take months/years before I get to this unless someone steps in to work on it.
Hello!
Using Flux, I deployed the external-secrets operator and its CRD.
The fact is that the external-secrets operator stores the
caBundle
directly in the CRD and therefore Flux constantly overwrites it.Question: is it possible to add some manifest fields to those ignored by Kustomization?