我的书签
添加书签
移除书签Tracking and Deployment Strategies
An Argo CD application spec provides several different ways of tracking Kubernetes resource manifests.
In all tracking strategies, the app has the option to sync automatically. If auto-sync is configured, the new resources manifests will be applied automatically — as soon as a difference is detected.
Note
In all tracking strategies, any parameter overrides take precedence over the Git state.
Helm
Helm chart versions are Semantic Versions. As a result, you can use any of the following version ranges:
| Use Case | How | Examples |
|---|---|---|
| Pin to a version (e.g. in production) | Use the version number | 1.2.0 |
| Track patches (e.g. in pre-production) | Use a range | 1.2. or >=1.2.0 <1.3.0 |
| Track minor releases (e.g. in QA) | Use a range | 1. or >=1.0.0 <2.0.0 |
| Use the latest (e.g. in local development) | Use star range | >=0.0.0 |
| Use the latest including pre-releases | Use star range with -0 suffix | -0 or >=0.0.0-0 |
Git
For Git, all versions are Git references but tags Semantic Versions can also be used:
| Use Case | How | Notes |
|---|---|---|
| Pin to a version (e.g. in production) | Either (a) tag the commit with (e.g. v1.2.0) and use that tag, or (b) using commit SHA. | See commit pinning. |
| Track patches (e.g. in pre-production) | Use a range (e.g. 1.2. or >=1.2.0 <1.3.0) | See tag tracking |
| Track minor releases (e.g. in QA) | Use a range (e.g. 1. or >=1.0.0 <2.0.0) | See tag tracking |
| Use the latest (e.g. in local development) | Use HEAD or master (assuming master is your master branch). | See HEAD / Branch Tracking |
| Use the latest including pre-releases | Use star range with -0 suffix | *-0 or >=0.0.0-0 |
HEAD / Branch Tracking
If a branch name, or a symbolic reference (like HEAD) is specified, Argo CD will continually compare live state against the resource manifests defined at the tip of the specified branch or the resolved commit of the symbolic reference.
To redeploy an app, make a change to (at least) one of your manifests, commit and push to the tracked branch/symbolic reference. The change will then be detected by Argo CD.
Tag Tracking
If a tag is specified, the manifests at the specified Git tag will be used to perform the sync comparison. This provides some advantages over branch tracking in that a tag is generally considered more stable, and less frequently updated, with some manual judgement of what constitutes a tag.
To redeploy an app, the user uses Git to change the meaning of a tag by retagging it to a different commit SHA. Argo CD will detect the new meaning of the tag when performing the comparison/sync.
But if you’re using semantic versioning you can set the constraint in your service revision and Argo CD will get the latest version following the constraint rules.
Commit Pinning
If a Git commit SHA is specified, the app is effectively pinned to the manifests defined at the specified commit. This is the most restrictive of the techniques and is typically used to control production environments.
Since commit SHAs cannot change meaning, the only way to change the live state of an app which is pinned to a commit, is by updating the tracking revision in the application to a different commit containing the new manifests. Note that parameter overrides can still be set on an app which is pinned to a revision.
