fix(argo-workflows): remove old default init service account (#834)

* fix(argo-workflows): remove old default init service account

Signed-off-by: GitHub <noreply@github.com>

* fix(argo-workflows): remove init.serviceAccount from README

Signed-off-by: GitHub <noreply@github.com>

* chore(argo-workflows): update changelog

Signed-off-by: GitHub <noreply@github.com>

* chore(argo-workflows): bump chart to 0.2.8

Signed-off-by: GitHub <noreply@github.com>

Co-authored-by: Vlad Losev <vladlosev@users.noreply.github.com>
This commit is contained in:
Zadkiel 2021-07-20 20:24:41 +02:00 committed by GitHub
parent 37277315ce
commit e393ef1ba2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 10 deletions

View file

@ -2,7 +2,7 @@ apiVersion: v2
name: argo-workflows
description: A Helm chart for Argo Workflows
type: application
version: 0.2.9
version: 0.2.10
appVersion: "v3.0.7"
icon: https://raw.githubusercontent.com/argoproj/argo-workflows/master/docs/assets/argo.png
home: https://github.com/argoproj/argo-helm
@ -15,6 +15,4 @@ maintainers:
- name: benjaminws
annotations:
artifacthub.io/changes: |
- "[Changed]: Service accounts, roles and role bindings can now be auto-created for each workflow controller namespace"
- "[Fixed]: The contributer testing guidelines were updated to reflect the chart name change from 'argo' to
'argo-workflows'"
- "[Fixed]: Removed init.serviceAccount unused fields"

View file

@ -10,7 +10,7 @@ This chart uses an install hook to configure the CRD definition. Installation of
A few options are:
- Manually create a ServiceAccount in the Namespace which your release will be deployed w/ appropriate bindings to perform this action and set the `init.serviceAccount` attribute
- Manually create a ServiceAccount in the Namespace which your release will be deployed w/ appropriate bindings to perform this action and set the `serviceAccountName` field in the Workflow spec
- Augment the `default` ServiceAccount permissions in the Namespace in which your Release is deployed to have the appropriate permissions
## Usage Notes

View file

@ -5,11 +5,6 @@ images:
pullSecrets: []
# - name: argo-pull-secret
init:
# By default the installation will not set an explicit one, which will mean it uses `default` for the namespace the chart is
# being deployed to. In RBAC clusters, that will almost certainly fail. See the NOTES: section of the readme for more info.
serviceAccount: ""
createAggregateRoles: true
## String to partially override "argo-workflows.fullname" template