base on Automatic container image update for Argo CD # Argo CD Image Updater  [](https://argocd-image-updater.readthedocs.io/en/latest/?badge=latest) [](https://codecov.io/gh/argoproj-labs/argocd-image-updater) [](https://goreportcard.com/report/github.com/argoproj-labs/argocd-image-updater) ## Introduction Argo CD Image Updater is a tool to automatically update the container images of Kubernetes workloads which are managed by Argo CD. In a nutshell, it will track image versions specified by annotations on the Argo CD Application resources and update them by setting parameter overrides using the Argo CD API. Currently it will only work with applications that are built using *Kustomize* or *Helm* tooling. Applications built from plain YAML or custom tools are not supported yet (and maybe never will). ## Documentation Read [the documentation](https://argocd-image-updater.readthedocs.io/en/stable/) for more information on how to setup and run Argo CD Image Updater and to get known to it's features and limitations. Above URL points to the documentation for the current release. If you are interested in documentation of upcoming features, check out the [the latest documentation](https://argocd-image-updater.readthedocs.io/en/latest/) which is up-to-date with the master branch. ## Current status Argo CD Image Updater is under active development. We would not recommend it yet for *critical* production workloads, but feel free to give it a spin. We're very interested in feedback on usability and the user experience as well as in bug discoveries and enhancement requests. **Important note:** Until the first stable version (i.e. `v1.0`) is released, breaking changes between the releases must be expected. We will do our best to indicate all breaking changes (and how to un-break them) in the [Changelog](CHANGELOG.md) ## Contributing You are welcome to contribute to this project by means of raising issues for bugs, sending & discussing enhancement ideas or by contributing code via pull requests. In any case, please be sure that you have read & understood the currently known design limitations before raising issues. Also, if you want to contribute code, please make sure that your code * has its functionality covered by unit tests (coverage goal is 80%), * is correctly linted, * is well commented, * and last but not least is compatible with our license and CLA Please note that in the current early phase of development, the code base is a fast moving target and lots of refactoring will happen constantly. ## License `argocd-image-updater` is open source software, released under the [Apache 2.0 license](https://www.apache.org/licenses/LICENSE-2.0) ## Things that are planned (roadmap) The following things are on the roadmap until the `v1.0` release * [ ] Extend Argo CD functionality to be able to update images for other types of applications. * [x] Extend Argo CD functionality to write back to Git * [ ] Provide web hook support to trigger update check for a given image * [x] Use concurrency for updating multiple applications at once * [x] Improve error handling * [x] Support for image tags with i.e. Git commit SHAs For more details, check out the [v1.0.0 milestone](https://github.com/argoproj-labs/argocd-image-updater/milestone/1) ## Frequently asked questions **Does it write back the changes to Git?** We're happy to announce that as of `v0.9.0` and Argo CD `v1.9.0`, Argo CD Image Updater is able to commit changes to Git. It will not modify your application's manifests, but instead writes [Parameter Overrides](https://argoproj.github.io/argo-cd/user-guide/parameters/#store-overrides-in-git) to the repository. We think that this is a good compromise between functionality (have everything in Git) and ease-of-use (minimize conflicts). **Are there plans to extend functionality beyond Kustomize or Helm?** Not yet, since we are dependent upon what functionality Argo CD provides for these types of applications. **Will it ever be fully integrated with Argo CD?** In the current form, probably not. If there is community demand for it, let's see how we can make this happen. There is [an open proposal](https://github.com/argoproj/argo-cd/issues/7385) to migrate this project into the `argoproj` org (out of the `argoproj-labs` org) and include it in the installation of Argo CD. ", Assign "at most 3 tags" to the expected json: {"id":"8325","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"