95f5605af7
- priority classes <-10 are ignored by cluster-autoscaler so QA jobs with too low priorities never run - start crawl priorities at 0 going down (same as before) - start qa run priorities at -2 going down (instead of -100) - this means a crawl of with scale of 3 can be preempted by 1st qa pod, but otherwise crawls have higher priority - rename priority classes as they are otherwise immutable and error on helm upgrade This allows for more room in lower pri classes for other type of objects, while keeping in mind the -10 and below threshold: (see: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md)
37 lines
721 B
YAML
37 lines
721 B
YAML
|
|
{{- range untilStep 0 (int .Values.max_crawl_scale) 1 }}
|
|
---
|
|
apiVersion: scheduling.k8s.io/v1
|
|
kind: PriorityClass
|
|
metadata:
|
|
name: crawl-pri-{{ . }}
|
|
value: {{ sub 0 . }}
|
|
globalDefault: false
|
|
description: "Priority for crawl instance #{{ . }}"
|
|
|
|
{{- end }}
|
|
|
|
{{- range untilStep 0 (int .Values.max_crawl_scale) 1 }}
|
|
---
|
|
apiVersion: scheduling.k8s.io/v1
|
|
kind: PriorityClass
|
|
metadata:
|
|
name: qa-crawl-pri-{{ . }}
|
|
value: {{ sub -2 . }}
|
|
globalDefault: false
|
|
description: "Priority for QA crawl instance #{{ . }}"
|
|
|
|
{{- end }}
|
|
|
|
# Lower Priority for Background Jobs
|
|
---
|
|
apiVersion: scheduling.k8s.io/v1
|
|
kind: PriorityClass
|
|
metadata:
|
|
name: bg-job
|
|
value: -1000
|
|
globalDefault: false
|
|
description: "Priority for background jobs"
|
|
|
|
|