No Prune Resources¶
You may wish to prevent an object from being pruned:
metadata: annotations: argocd.argoproj.io/sync-options: Prune=false
In the UI, the pod will simply appear as out-of-sync:
The sync-status panel shows that pruning was skipped, and why:
The app will be out of sync if Argo CD expects a resource to be pruned. You may wish to use this along with compare options.
Disable Kubectl Validation¶
For a certain class of objects, it is necessary to
kubectl apply them using the
--validate=false flag. Examples of this are kubernetes types which uses
RawExtension, such as ServiceCatalog. You can do using this annotations:
metadata: annotations: argocd.argoproj.io/sync-options: Validate=false
If you want to exclude a whole class of objects globally, consider setting
resource.customizations in system level configuration.
Skip Dry Run for new custom resources types¶
When syncing a custom resource which is not yet known to the cluster, there are generally two options:
1) The CRD manifest is part of the same sync. Then ArgoCD will automatically skip the dry run, the CRD will be applied and the resource can be created.
2) In some cases the CRD is not part of the sync, but it could be created in another way, e.g. by a controller in the cluster. An example is gatekeeper,
which creates CRDs in response to user defined
ConstraintTemplates. ArgoCD cannot find the CRD in the sync and will fail with the error
the server could not find the requested resource.
To skip the dry run for missing resource types, use the following annotation:
metadata: annotations: argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true
The dry run will still be executed if the CRD is already present in the cluster.