The e2e install still flakes on a busy runner where components reach
readiness but overshoot tight wait budgets:
- keycloak HR chain (keycloak-db CNPG -> keycloak StatefulSet ->
keycloak-configure) reaches Ready ~15-18m in: 10m -> 20m.
- tenant aggregate wait (hr/etcd hr/ingress hr/monitoring hr/seaweedfs
hr/tenant-root): the tenant stack only starts creating pods ~9-10m in
and then needs several more minutes: 10m -> 20m.
- per-app tenant readiness waits (ingress, etcd, VictoriaLogs/Metrics
clusters, grafana-db, grafana): 5m -> 10m.
Diagnosed via a live SSH breakpoint: the HRs all do reach Ready, just
outside the old budgets.
Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Andrei Kvapil <andrei.kvapil@aenix.io>