ServiceAcct not correctly applied to workflow
davemasselink opened this issue · 0 comments
davemasselink commented
Describe the bug
When a serviceAccount is passed to the HealthCheck in spec, this same account should be applied to the argo workflows which the controller is creating. In this way, it will be passed down to the running pod where the account will actually be used
To Reproduce
If we cannot reproduce, we cannot fix! Steps to reproduce the behavior:
- Craft a healthcheck which uses the serviceAccount property.
- Submit healthcheck via
kubectl create -f <filename>
- Inspect the workflow with
argo get <workflowName>
- See that the
default
account was applied regardless of configured serviceAccount
Expected behavior
Configured serviceAccount should be set on workflow
Version
all