Related to swh/infra/sysadm-environment#5212

The moma instance had around of 1G of memory allowed.

The 256m in the kubernetes environment are probably not enough

Related to swh/infra/sysadm-environment#5212

Refs. swh/infra/sysadm-environment#5211

Refs. swh/infra/sysadm-environment#5211

Refs. swh/infra/sysadm-environment#5211

Refs. swh/infra/sysadm-environment#5211

This allows using it for the cassandra webapp as well

The nginx is not notified as soon a service endpoints are updated so it
sends a couple of requests to a terminated pod.
It's not a problem for idempotent request as nginx retry on another pod
but it's not the case by default for POST requests.

The option is activated by default for all the ingresses because
POST requests are used everywhere

Related to swh/infra/sysadm-environment#5210

Refs. swh/infra/sysadm-environment#5194

This matches what used to be done in the previous deposit (moma) instance.

Refs. swh/infra/sysadm-environment#5207

It used the storageConfigurationRef key instead of the dedicated
storageMetadataConfigurationRef.

Refs. swh/infra/sysadm-environment#5207

Refs. swh/infra/sysadm-environment#5205

Refs. swh/infra/sysadm-environment#5205

Refs. swh/infra/sysadm-environment#5205

Refs. swh/infra/sysadm-environment#5205

Refs. swh/infra/sysadm-environment#5205

This also fixes an existing wrong configuration regarding the cluster network ranges.

Refs. swh/infra/sysadm-environment#5205

Fix the typo for fun and profit.

Refs. swh/infra/sysadm-environment#5205

Refs. swh/infra/sysadm-environment#5205

Refs. swh/infra/sysadm-environment#5205

Refs. swh/infra/sysadm-environment#5194

Refs. swh/infra/sysadm-environment#5194

To solve the remaining keycloak authentication issue in the new dynamic webapp.

Refs. swh/infra/sysadm-environment#5194
Refs. swh/infra/sysadm-environment#5095
Refs. c22ffb07

The reverse proxy is the one in charge of this.

Refs. swh/infra/sysadm-environment#5194

It's one step towards migrating the main archive webapp to the dynamic infrastructure.

Refs. swh/infra/sysadm-environment#5194

It's a first step towards decomissionning the gunicorn swh service from moma.

Refs. swh/infra/sysadm-environment#5194

Probably broken during a previous iteration with a rebase which swapped things up
(& silently unnoticed).

Refs. swh/infra/sysadm-environment#5194

This reverts commit 6e3416e8.

Refs. swh/infra/sysadm-environment#5194

The client id is only useful for debugging, but let's make it meaningful.

The journal_writer config needs to be under the indexer_storage key,
rather than at the toplevel.

It's the reverse proxy which has one, the ingress does not need it. Internally, we only
use http connection to communicate.

Refs. swh/infra/sysadm-environment#5194

Refs. swh/infra/sysadm-environment#5191

As a first step towards migrating the dynamic instance as the main public one.

Refs. swh/infra/sysadm-environment#5191