We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe.
The current Argo plugin launches all jobs using the default user which requires the patch pod permission.
default
patch pod
Describe the solution you'd like
We shall allow users to specify a service account in the workflow definition as an argument that gets passed to the Argo plugin.
The text was updated successfully, but these errors were encountered:
I believe this is possible by setting it in the Argo definition workflow.spec.serviceAccountName
workflow.spec.serviceAccountName
re. https://github.com/argoproj/argo-workflows/blob/7abead2a564876a695201cf7539bd20d1fc67888/docs/workflow-rbac.md
Sorry, something went wrong.
Moving this to the 0.3.0 milestone as this won't be done for 0.2.0, but as Neil suggests this can be configured in the Argo workflow Template.
We may have a future API call to add a ARGO Workflow template to ARGO, at which time, we will look to investigate this further.
No branches or pull requests
Is your feature request related to a problem? Please describe.
The current Argo plugin launches all jobs using the
default
user which requires thepatch pod
permission.Describe the solution you'd like
We shall allow users to specify a service account in the workflow definition as an argument that gets passed to the Argo plugin.
The text was updated successfully, but these errors were encountered: