-
Notifications
You must be signed in to change notification settings - Fork 884
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manage ArgoCD Image Updater lifecycle in the ArgoCD Operator #773
Comments
Hi @juv , we have this in our backlog list. I think we should get this done in the next release. |
cc: @jaideepr97 |
@iam-veeramalla sounds great, looking forward to using this in our Openshift ArgoCD Operator 🚀 |
I don't have the exact release date yet, we are targeting something around 1st or 2nd week of November. |
hi @juv |
Is your feature request related to a problem? Please describe.
When using the ArgoCD Operator, a lot of ArgoCD resources and their lifecycle can be managed by the Operator. Currently, the ArgoCD Image Updater resources need to be installed to the Kubernetes cluster manually. Mixing in a manual deployment process for some parts of the ArgoCD ecosystem gets hard to maintain and is unexpected from a user perspective. Changes in ArgoCD that require a re-configuration of the ArgoCD Image Updater resources will need to be resolved manually by the user, while the rest of the ArgoCD ecosystem is managed by the Operator.
Describe the solution you'd like
Implement the lifecycle management of ArgoCD Image Updater resources by the ArgoCD Operator, in a similar way that is being offered for the ApplicationSet Controller.
Describe alternatives you've considered
/
Additional context
/
The text was updated successfully, but these errors were encountered: