Releases: argoproj-labs/argocd-image-updater
v0.5.0
Release description
This release brings mainly bug fixes and other enhancements. The most obvious changes are:
- It's now possible to follow non-semver formatted tags when using update strategy
latest
- Adds the possibility to track the same image multiple times for different targets in the same application
Upgrade notes (no really, you MUST read this)
argocd-image-updater
now comes with default RBAC rules for the service account, to enable reading of secrets from the namespace the pod is running in. It is advised to install the updated manifests.
Bug fixes
- fix: Do not constraint tags to semver if update strategy is latest
- fix: Multiple same images in the same application not possible
New features
- feat: Allow filtering applications by name patterns
Other changes
- enhancement: Slightly increase verbosity in default log level
- enhancement: Provide default RBAC rules for serviceaccount
- enhancement: Warm-up cache before starting image cycle
v0.4.0
Release description
This release brings several new features as well as bug fixes.
The major new features in this release are the ability to specify per-image pull secrets via an annotation, i.e. argocd-image-updater.argoproj.io/myimage.pull-secret: secret:mynamespace/mysecret#somefield
and the pre-filtering of tags returned by the registry. The latter feature allows you to exclude specific tags from being considered for update.
Also, GitHub Docker Registry is now supported.
Upgrade notes (no really, you MUST read this)
N/A
Bug fixes
- fix: Properly load registry configuration
- fix: Use a default path for registries.conf
- fix: Make installation base compatible with Kustomize v2
New features
- feat: Allow filtering of tags using built-in filter functions
- feat: Allow specifying per-image pull secrets
- feat: Support GitHub Docker registry
Other changes
- refactor: Lots of refactoring "under the hood"
v0.3.1
v0.3.0
Release description
The major new feature for this release is the introduction of update strategies:
- The strategy
latest
will evaluate the creation date and chose the latest created tag matching the version constraint for update - The strategy
name
will pick the last found tag according to alphabet sorting - The strategy
semver
(the default) will pick the latest allowed version according to version constraint
Also, this release introduces a simple in-memory cache for tag meta data and the code has seen some refactoring. Please see below for breaking changes and a complete list of things that have been done.
Upgrade notes (no really, you MUST read this)
- Syntax change for running:
argocd-image-updater run [flags]
instead ofargocd-image-updater [flags]
has now to be used - Attention: Helm annotation names have changed from
<image_alias>.image-{name,tag,spec}
to<image_alias>.helm.image-{name,tag,spec}
- Specifying target image name for Kustomize applications now require their own annotation, the image alias is not re-used for this anymore
Bug fixes
- fix: Possible race while waiting for app updating goroutines
New features
- feat: Allow setting the upgrade strategy for images via annotation
Other changes
- refactor: Change run behaviour by providing
run
andversion
commands - enhancement: Provide a
version
command to print out version information - enhancement: Allow storing metadata for image tags
- enhancement: Fetch tag metadata along with tags and store creation timestamp
- enhancement: Introduce simple cache for immutable metadata
- refactor: Make version constraints parametrizable
- enhancement: Allow sorting of tags by semver, date or name
- refactor: Give annotation names their own namespace-like living room
- enhancement: Kustomize target image name got its own annotation