adding priority class support for argo-server and workflow-controller deployments

This commit is contained in:
Manjunath Shenoy 2020-07-14 12:29:08 -04:00
parent bc78e3cbe1
commit fa90940efa
3 changed files with 8 additions and 0 deletions

View file

@ -25,6 +25,8 @@ spec:
annotations:
{{ toYaml .Values.server.podAnnotations | indent 8}}{{- end }}
spec:
{{- if .Values.server.priorityClassName }}
priorityClassName: {{ .Values.server.priorityClassName | quote }}
serviceAccountName: {{ .Values.server.serviceAccount | quote }}
containers:
- name: argo-server

View file

@ -25,6 +25,8 @@ spec:
annotations:
{{ toYaml .Values.controller.podAnnotations | indent 8}}{{- end }}
spec:
{{- if .Values.controller.priorityClassName }}
priorityClassName: {{ .Values.controller.priorityClassName | quote }}
serviceAccountName: {{ .Values.controller.serviceAccount | quote }}
containers:
- name: controller

View file

@ -108,6 +108,8 @@ controller:
nodeSelector: {}
tolerations: []
affinity: {}
## Replace system_priority_class with your priorityClassName. See https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass
priorityClassName: system_priority_class
# executor controls how the init and wait container should be customized
executor:
@ -218,6 +220,8 @@ server:
# key: client-secret
## The OIDC redirect URL. Should be in the form <argo-root-url>/oauth2/callback.
# redirectUrl: https://argo/oauth2/callback
## Replace system_priority_class with your priorityClassName. See https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass
priorityClassName: system_priority_class
# Influences the creation of the ConfigMap for the workflow-controller itself.
useDefaultArtifactRepo: false