-
Notifications
You must be signed in to change notification settings - Fork 272
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
Image Updater does not work with "App in any namespace" Argo configuration #601
Comments
Is there an update to this? This is a huge problem and basically defeats the purpose of the image updater if you can't use it in any namespaces outside of where argocd is installed. The documentation should reflect this. |
This issue should now be solved through: #763 |
I think #763 hasn't solved this issue. (I have tested the master branch and it looks like I'm correct) I think the root cause is here https://github.com/argoproj-labs/argocd-image-updater/blob/master/cmd/run.go#L113, the kubeclient defined here is restricted to the argocd namespace. I think perhaps we can try with Updates: I got the API approach worked in my environment. |
Signed-off-by: Jort Koopmans <[email protected]>
- Modify ks8Client functions to always get Application resources across all namespaces - Add required RBAC permissions Signed-off-by: Jort Koopmans <[email protected]>
I've also encountered this issue (v0.14.0 and built from master). I've added a draft PR that aims to help pinpointing the issue and working towards a solution. Since I think there are some design decisions that need to be taken, I'm looking forward to your feedback 😃 . |
@chengfang ; Since you're aware of this issue (from your comment on another ticket), what is your view on the resolution direction? |
- Modify ks8Client functions to always get Application resources across all namespaces - Add required RBAC permissions Signed-off-by: Jort Koopmans <[email protected]>
any progress on the issue? this is a must for us to provide the feature to the users. |
Signed-off-by: Jort Koopmans <[email protected]>
…goproj-labs#854) Signed-off-by: Jort Koopmans <[email protected]> Signed-off-by: Tchoupinax <[email protected]>
Describe the bug
App in any namespace is a set of Argo feature allowing you to have
Application
resources in other namespaces thanargocd
.This setup is not supported by Image Updater
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Image Updater detects the Application in other namespaces than
argocd
Additional context
As the Application was not detected using the
kubernetes
application API, I tried switching toapplications_api: argocd
.I ensured that Argo could update the apps by updating the RBAC role as described in the official App in Any namespace doc.
In this mode, it correctly detects the Argo Application, updates it (see above), but then it fails to update the parameter in Argo, because it does not pass the namespace of the app, and Argo uses
argocd
by default when no namespace is specified (see logs below).Version
0.12.2
Logs
Those logs are after configuring
applications_api: argocd
argocd-image-updater
logs:Note that the namespace for the app does not appear anywhere here.
argocd-server
logs:The error is here:
msg="application does not exist" application=test-image namespace=argocd
(namespace is incorrect)The text was updated successfully, but these errors were encountered: