feat(argo-rollouts): Allow additional containers in controller deployment (#999)

* feat: Allow additional containers in controller deployment

Our local metrics setup uses an extra container for the controller
deployment. Adding this in case others have a similar use case.

Signed-off-by: Brian Johnson <b2jrock@gmail.com>

* Apply suggesstions from code review

Signed-off-by: Brian Johnson <b2jrock@gmail.com>

* Bump minor version

Signed-off-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>

Co-authored-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>
This commit is contained in:
Brian Johnson 2021-11-09 12:49:48 -08:00 committed by GitHub
parent b8c689e3c7
commit 5e18356d25
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 10 additions and 2 deletions

View file

@ -39,6 +39,7 @@ If dashboard is installed by `--set dashboard.enabled=true`, checkout the argo-r
| controller.image.repository | string | `"argoproj/argo-rollouts"` | Repository to use |
| controller.image.tag | string | `""` | Overrides the image tag (default is the chart appVersion) |
| controller.extraArgs | list | `[]` | Additional arguments for the controller. A list of flags. |
| controller.extraContainers | list | `[]` | Literal yaml for extra containers to be added to controller deployment. |
| controller.resources | object | `{}` | Resource limits and requests for the controller pods. |
| controller.tolerations | list | `[]` | [Tolerations for use with node taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) |
| controller.affinity | object | `{}` | [Assign custom affinity rules to the deployment](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/) |