fix(argo-workflows): Clarify the purpose of the aggregate roles in the values.yaml (#3193)
Signed-off-by: Tim Collins <tim@thecollins.team>
This commit is contained in:
parent
cf172edb3f
commit
a774ae2e6e
3 changed files with 5 additions and 5 deletions
|
|
@ -116,7 +116,7 @@ Fields to note:
|
|||
| crds.annotations | object | `{}` | Annotations to be added to all CRDs |
|
||||
| crds.install | bool | `true` | Install and upgrade CRDs |
|
||||
| crds.keep | bool | `true` | Keep CRDs on chart uninstall |
|
||||
| createAggregateRoles | bool | `true` | Create clusterroles that extend existing clusterroles to interact with argo-cd crds |
|
||||
| createAggregateRoles | bool | `true` | Create ClusterRoles that extend existing ClusterRoles to interact with Argo Workflows CRDs. |
|
||||
| emissary.images | list | `[]` | The command/args for each image on workflow, needed when the command is not specified and the emissary executor is used. |
|
||||
| extraObjects | list | `[]` | Array of extra K8s manifests to deploy |
|
||||
| fullnameOverride | string | `nil` | String to fully override "argo-workflows.fullname" template |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue