My ApplicationSets manage both cluster services and application deployments, but chart versions and image tags are starting to get stale. I also need to detect new OCI artifacts, including migration images.
Kargo looks useful but verbose for a simple tag change, and Argo CD Image Updater seems to add a lot of annotations. What patterns work for keeping updates reviewed and moving them through environments?
8r!parcelcog_237:
How would you handle different versions in staging and production?
9m+drivnexa_682:
Keep the desired version for each environment in Git and decide separately how a tested version gets promoted to production. A dependency update tool can propose changes, but it does not by itself define your promotion policy.