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
Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
What happened:
I tried to run a workflow step that creates output artifacts. This runs fine if the service account being used to run the workflows has root permissions. However, if the account does not have permissions to write to the root directory /, the workflow step will fail with the below error message:
I expect the pod to write the output artifact, even if the service account being used does not have root permissions. I should not have to run as root in order to write output artifacts.
How to reproduce it (as minimally and precisely as possible):
Submit a workflow to argo, which has a step with an output artifact. Make sure the service account for the executor pod does not have permissions to write to the root directory. This can be done by adding the service account to spec.serviceAccount in the workflow yaml.
The text was updated successfully, but these errors were encountered:
alexcapras
changed the title
Unable to write output artifact to MinIO when service account has limited permissions
Unable to write output artifacts when service account has limited permissions
Jul 1, 2019
Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
What happened:
I tried to run a workflow step that creates output artifacts. This runs fine if the service account being used to run the workflows has root permissions. However, if the account does not have permissions to write to the root directory
/
, the workflow step will fail with the below error message:What you expected to happen:
I expect the pod to write the output artifact, even if the service account being used does not have root permissions. I should not have to run as root in order to write output artifacts.
How to reproduce it (as minimally and precisely as possible):
Submit a workflow to argo, which has a step with an output artifact. Make sure the service account for the executor pod does not have permissions to write to the root directory. This can be done by adding the service account to
spec.serviceAccount
in the workflow yaml.Anything else we need to know?:
No.
Environment:
Other debugging information (if applicable):
The text was updated successfully, but these errors were encountered: