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:
parent
b8c689e3c7
commit
5e18356d25
4 changed files with 10 additions and 2 deletions
|
|
@ -52,6 +52,9 @@ spec:
|
|||
{{- toYaml .Values.containerSecurityContext | nindent 10 }}
|
||||
resources:
|
||||
{{- toYaml .Values.controller.resources | nindent 10 }}
|
||||
{{- with .Values.controller.extraContainers }}
|
||||
{{- toYaml . | nindent 6 }}
|
||||
{{- end }}
|
||||
{{- if .Values.controller.nodeSelector }}
|
||||
nodeSelector:
|
||||
{{- toYaml .Values.controller.nodeSelector | nindent 8 }}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue