DevFW-CICD/argocd-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(argo-cd): Add priorityClassName to notifications (#1439)

Browse source 
Allow to set up a priorityClassName for notifications controller Pods

Signed-off-by: Paweł Kalemba <pawel.kalemba@getresponse.com>

Signed-off-by: Paweł Kalemba <pawel.kalemba@getresponse.com>
This commit is contained in:
Paweł Kalemba 2022-09-06 12:13:28 +02:00 • committed by GitHub
parent 0bac122e98
commit db0957d3cb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 9 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

1
charts/argo-cd/README.md
View file

@ -960,6 +960,7 @@ If you want to use an existing Redis (eg. a managed service from a cloud provide
| notifications.notifiers | object | See [values.yaml] | Configures notification services such as slack, email or custom webhook |
| notifications.podAnnotations | object | `{}` | Annotations to be applied to the controller Pods |
| notifications.podLabels | object | `{}` | Labels to be applied to the controller Pods |
| notifications.priorityClassName | string | `""` | Priority class for the controller pods |
| notifications.resources | object | `{}` | Resource limits and requests for the controller |
| notifications.secret.annotations | object | `{}` | key:value pairs of annotations to be added to the secret |
| notifications.secret.create | bool | `true` | Whether helm chart creates controller secret |