Kirill Ilin 218384ed32 feat(keycloak): let Keycloak and its database proxy spread across zones ...

Neither the Keycloak StatefulSet nor the keycloak-kms-proxy Deployment
exposed any placement, so the scheduler was free to put both replicas of
each in one failure domain. For Keycloak that is worse than it looks: a
StatefulSet does not replace a pod stuck on an unreachable node, so losing
that domain takes every replica for as long as it stays lost.

Expose affinity and topologySpreadConstraints for both, empty by default
so nothing changes unless an installation opts in, and give the proxy a
PodDisruptionBudget once it runs more than one replica.

Assisted-By: LLM
Signed-off-by: Kirill Ilin <stitch14@yandex.ru>

2026-09-30 14:07:22 +05:00

..

apps

fix(kubernetes): fail the OIDC bootstrap Job when the tenant CA is missing (#4232)

2026-09-30 01:50:22 +03:00

core

fix(platform): make mongodb-application depend on its operator

2026-09-30 02:18:28 +03:00

extra

fix(cozy-lib): round the sanitized CPU request up to a whole milli-CPU

2026-09-29 17:04:00 +02:00

library

fix(cozy-lib): round the sanitized CPU request up to a whole milli-CPU

2026-09-29 17:04:00 +02:00

system

feat(keycloak): let Keycloak and its database proxy spread across zones

2026-09-30 14:07:22 +05:00

tests/cozy-lib-tests

fix(cozy-lib): round the sanitized CPU request up to a whole milli-CPU

2026-09-29 17:04:00 +02:00