You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I've upgraded from 0.12.0 to 0.15.0.
Previously no cluster roles were required.
Upon startup, i get the following errors
ttime="2024-10-30T12:53:25Z" level=error msg="error while communicating with ArgoCD" argocd_server=argocd-server.argocd grpc_web=true grpc_webroot= insecure=false plaintext=false
time="2024-10-30T12:53:25Z" level=error msg="Error: error listing applications: applications.argoproj.io is forbidden: User \"system:serviceaccount:argocd:argocd-image-updater\"
This is when running in kubernetes-api mode (so the initial complaints about ArgoCD are also strange...)
To Reproduce
Run the latest image against official helm chart and ensure createClusterRoles: false.
Expected behavior
I would expect the role-bindings shipped with the helm chart should work. I'm also curious to know why the clusterrole needs update/patch?
Additional context
I'm not sure whether this is a helm-chart issue, or whether the actual code should support only handling applications from the deployed namespace (in our case argocd). All of our application resources are in this namespace.
Ideally it would be nice to have the option here. That still might be covered by the RBAC though rather than app-code, so could still be a helm issue.
Describe the bug
I've upgraded from 0.12.0 to 0.15.0.
Previously no cluster roles were required.
Upon startup, i get the following errors
This is when running in kubernetes-api mode (so the initial complaints about ArgoCD are also strange...)
To Reproduce
Run the latest image against official helm chart and ensure
createClusterRoles: false
.Expected behavior
I would expect the role-bindings shipped with the helm chart should work. I'm also curious to know why the clusterrole needs update/patch?
Additional context
I'm not sure whether this is a helm-chart issue, or whether the actual code should support only handling applications from the deployed namespace (in our case
argocd
). All of our application resources are in this namespace.Ideally it would be nice to have the option here. That still might be covered by the RBAC though rather than app-code, so could still be a helm issue.
I believe the error comes from
argocd-image-updater/pkg/argocd/argocd.go
Line 35 in a5acd25
and is a result of #854
Version
v.015.0 - was not present in v0.12.0
The text was updated successfully, but these errors were encountered: