-
Notifications
You must be signed in to change notification settings - Fork 2k
Labels
Description
Describe the bug
With the flag workflow.serviceAccount.create
a service account with the name argo-workflow is created without a corresponding service account secret. This secret however is requested when creating a workflow step with the http template.
Related helm chart
argo-workflows
Helm chart version
0.45.0
To Reproduce
- Install argo-workflows chart with values
workflow.serviceAccount.create=true
andworkflow.rbac.agentPermissions=true
- create a workflow with a step using the http template
- start the workflow
The http step is keeps stuck in a pending state. When checking the pods which are created there is a pod in the state PodInitializing with the error "secret "argo-workflow.service-account-token" not found".
After creating this secret manually everything works fine:
apiVersion: v1
kind: Secret
type: kubernetes.io/service-account-token
metadata:
name: argo-workflow.service-account-token
annotations:
kubernetes.io/service-account.name: "argo-workflow"
Expected behavior
I would expect the chart to create the service account secret since this is required by the agent pods.
Screenshots
No response
Additional context
No response