mirror of
https://github.com/argoproj/argo-cd
synced 2026-05-24 09:50:08 +00:00
59 lines
2.2 KiB
Markdown
59 lines
2.2 KiB
Markdown
# Sync Options
|
|
|
|
## No Prune Resources
|
|
|
|
>v1.1
|
|
|
|
You may wish to prevent an object from being pruned:
|
|
|
|
```yaml
|
|
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](compare-options.md).
|
|
|
|
## Disable Kubectl Validation
|
|
|
|
>v1.2
|
|
|
|
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](https://github.com/kubernetes-incubator/service-catalog/blob/master/pkg/apis/servicecatalog/v1beta1/types.go#L497). You can do using this annotations:
|
|
|
|
|
|
```yaml
|
|
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](../user-guide/diffing.md#system-level-configuration).
|
|
|
|
## Skip Dry Run for new custom resources types
|
|
|
|
>v1.6
|
|
|
|
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](https://github.com/open-policy-agent/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:
|
|
|
|
```yaml
|
|
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.
|