AKS Flux Extension - One shot reconcile #5157
-
Hi all, I'm trying to use the AKS flux extension to bootstrap my cluster into Rancher via a kubernetes manifest. I'm using Azure blobstore as my source and I'm able to populate it with the kube manifest and have Flux apply it via kustomize operation. However, once the resources are deployed the Rancher bootstrap takes over and modifies them according to its needs. What I need is a way to tell Flux to stop reconciling after the initial deployment. I've tried patching the resources to include the annotation:
It seems that when that's present in a manifest, flux won't even deploy the resources in the first place. I've also tried using a dependent kustomize patch to patch Short of setting the sync interval to its absolute max. Is there any way I can manage this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
You can use the annotation: See the docs here: https://fluxcd.io/flux/components/kustomize/kustomizations/#controlling-the-apply-behavior-of-resources |
Beta Was this translation helpful? Give feedback.
You can use the annotation:
kustomize.toolkit.fluxcd.io/ssa: IfNotPresent
See the docs here: https://fluxcd.io/flux/components/kustomize/kustomizations/#controlling-the-apply-behavior-of-resources