Refs. swh/infra/sysadm-environment#5512

The runner only schedules a subset of registered task types (e.g. lister,
{check|load}-deposit, cooker). The rest are just not its concern anymore.

Refs. swh/infra/sysadm-environment#5512

Refs. swh/infra/sysadm-environment#5512

To check whether that makes a difference in the queries sent to the backend.

Refs. swh/infra/sysadm-environment#5512

Refs. swh/infra/sysadm-environment#5512

There are some usage peak from time to time where we exceed the current number
of requests our current replicas can handle. This is to reduce 502 errors.

Refs. swh/infra/sysadm-environment#5512

[1] https://grafana.softwareheritage.org/goto/_jpCQOhHk?orgId=1

Refs. swh/infra/sysadm-environment#5512

Refs. swh/infra/sysadm-environment#5512

It was misindented from 2 characters.

Otherwise, we schedule and fill-in queues which are not consumed. This then
escalates to spurious infra alerts.

Those loaders were stopped to avoid running too much loaders in the staging infra.

It's mostly the same way to trigger it. Only some configuration manipulation
must slightly be adapted to allow the extra service to deploy it.

The scheduler-runner already allows it but it was used only in the
`start-runner --with-priority` call. Now, we'll be able to run if for both.

This is just the list of task types so name it properly.

The kubernetes scheduler should do the right thing.

Refs. swh/infra/sysadm-environment#5593

That pvc/pv will be accessible from 2 pods objstorage-{ro,rw} on the same
host.

Refs. swh/infra/sysadm-environment#5593

Avoid using ceph storage. It should be used for programs that does a moderate
amount of I/O but still needs "singleton" persistence.

Objstorage can be I/O intensive.

This reverts commit 33eac1f7.

Refs. swh/infra/sysadm-environment#5593

The local-persistent does not support the accessMode ReadWriteMany

Refs. swh/infra/sysadm-environment#5593

PV does not declare namespace.

Refs. swh/infra/sysadm-environment#5593

Add one objstorage-pathslicing-pvc to manage the next-version objstorage.
That way, the data stored won't get decommissionned when the argocd
next-version is stopped.

Refs. swh/infra/sysadm-environment#5593

As in objstorage, alter, etc...

Refs. swh/infra/sysadm-environment#5593

As objstorage, alter, etc... does

Refs. swh/infra/sysadm-environment#5593

Refs. swh/infra/sysadm-environment#5593

Refs. swh/infra/sysadm-environment#5593

Refs. swh/infra/sysadm-environment#5593