-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
executor plugins example from documentation does not work #13015
Comments
Changing the I will create an PR with the updated documentation and add some more noes about the RBAC expectations for the SA running those tasks. Hopefully this will save some time to the next one trying the examples from the documentation. |
In the code it seems to use whatever SA the Workflow has set. You haven't set it in your Workflow (or |
Yes, I thought the same, so I'm not sure why I encountered that error. I will investigate it further when I have more time. |
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened/what did you expect to happen?
Executor_plugins example provided in the documentation does not work even after adjusting the default service account permissions.
To setup the initial environment I followed the quick guide steps and updated
default
service account RBAC permissions.Also it's odd that the logs are complaining about
system:serviceaccount:argo:argo
permissions, even If I am not setting the service account toargo
in the Workflow. Based on the documentation it should usedefault
.Version
latest
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: