fix(argo-workflows): Make Argo Agent and Artifact GC permissions optional for workflows SA (#3048)

This commit is contained in:
Tim Collins 2024-11-22 15:19:46 +00:00 committed by GitHub
parent e888b374c9
commit 90eef9ef1f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
8 changed files with 124 additions and 17 deletions

View file

@ -133,6 +133,8 @@ Fields to note:
| Key | Type | Default | Description |
|-----|------|---------|-------------|
| workflow.namespace | string | `nil` | Deprecated; use controller.workflowNamespaces instead. |
| workflow.rbac.agentPermissions | bool | `false` | Allows permissions for the Argo Agent. Only required if using http/plugin templates |
| workflow.rbac.artifactGC | bool | `false` | Allows permissions for the Argo Artifact GC pod. Only required if using artifact gc |
| workflow.rbac.create | bool | `true` | Adds Role and RoleBinding for the above specified service account to be able to run workflows. A Role and Rolebinding pair is also created for each namespace in controller.workflowNamespaces (see below) |
| workflow.rbac.serviceAccounts | list | `[]` | Extra service accounts to be added to the RoleBinding |
| workflow.serviceAccount.annotations | object | `{}` | Annotations applied to created service account |