browsertrix/chart/templates/priorities.yaml
Ilya Kreymer fb3d88291f
Background Jobs Work (#1321)
Fixes #1252 

Supports a generic background job system, with two background jobs,
CreateReplicaJob and DeleteReplicaJob.
- CreateReplicaJob runs on new crawls, uploads, profiles and updates the
`replicas` array with the info about the replica after the job succeeds.
- DeleteReplicaJob deletes the replica.
- Both jobs are created from the new `replica_job.yaml` template. The
CreateReplicaJob sets secrets for primary storage + replica storage,
while DeleteReplicaJob only needs the replica storage.
- The job is processed in the operator when the job is finalized
(deleted), which should happen immediately when the job is done, either
because it succeeds or because the backoffLimit is reached (currently
set to 3).
- /jobs/ api lists all jobs using a paginated response, including filtering and sorting
- /jobs/<job id> returns details for a particular job
- tests: nightly tests updated to check create + delete replica jobs for crawls as well as uploads, job api endpoints
- tests: also fixes to timeouts in nightly tests to avoid crawls finishing too quickly.

---------
Co-authored-by: Tessa Walsh <tessa@bitarchivist.net>
2023-11-02 13:02:17 -07:00

25 lines
457 B
YAML

{{- range untilStep 0 (int .Values.max_crawl_scale) 1 }}
---
apiVersion: scheduling.k8s.io/v1
kind: PriorityClass
metadata:
name: crawl-instance-{{ . }}
value: -{{ . }}
globalDefault: false
description: "Priority for crawl instance #{{ . }}"
{{- end }}
# Lower Priority for Background Jobs
---
apiVersion: scheduling.k8s.io/v1
kind: PriorityClass
metadata:
name: bg-jobs
value: -100
globalDefault: false
description: "Priority for background jobs"