-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
User "system:serviceaccount:argo:default" cannot patch resource "pods" in API group "" in the namespace "argo"
#12783
Comments
User "system:serviceaccount:argo:default" cannot patch resource "pods" in API group "" in the namespace "argo"
You need to set proper RBAC for Pods of a Workflow: https://argo-workflows.readthedocs.io/en/latest/workflow-rbac/.
This is duplicative of #12391 (comment) et al -- this was always required in the docs but simple steps were able to bypass this before v3.5.2. |
@agilgur5 Hello, I would appreciate some kind of documentation about "workflowtaskresults" Resource. |
Duplicate of #11167. It's not user-facing, it's used by the Executor and Controller to communicate with each other. |
Hi, |
Yes technically, if they are in the same namespace. You don't say whether this is something you desire to do, or something you're trying to prevent. |
@Joibel I would like to be able to reproduce this case. And to prevent it. I saw the only change between running and succeded WF in WorkflowTaskResult CR is |
Pre-requisites
:latest
What happened/what did you expect to happen?
WF template: https://argo-workflows.readthedocs.io/en/latest/walk-through/hello-world/
Version: v3.5.1 - no error
Version: v3.5.2 and higher- with error
Error:
Version
v3.5.2
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: