Image version constraints for ApplicationSets

[mtweeman]

Hey,

Let's say I have one ApplicationSet that produces all Applications for me. Is it possible to specify version constraints for the images that work across various images versions?

For example:
Application A contains image: app-a:1.0.0
Application B contains image: app-b:2.0.0

The images work well together. Is it possible to specify version constraint that prevents "major" update? Consider annotation in form argocd-image-updater.argoproj.io/image-list: "my-org/{{index .path.segments 1}}" which is generic. 1st path segment reflects app name which equals to image name.

[chengfang]

Please see image-updater docs on semver: https://argocd-image-updater.readthedocs.io/en/latest/basics/update-strategies/#semver-update-to-semantic-versions . With semver, one can specify to upgrade only patch version, minor version or major version.

[mtweeman]

My question is more general I think. I don't intend to specify 1.x for app-a and 2.x for app-b. I'd like to know if there's a way to specify "major" in some way in ApplicationSet. That way, I don't need to explicitly list all images that are version constrained in image list, like:
argocd-image-updater.argoproj.io/image-list: "my-org/app-a:1.x,my-org/app-b:2.x"
With many images, the maintenance is cumbersome in such case.

[chengfang]

Okay, I see. I don't think this is supposed in either image-updater or appset. I also have doubt over the long-term maintenance cost of this approach. These images are not uniform in their release cycles and life spans, and I'm sure if it's practically viable to apply the same general policy like "major" to all images.