Switch receiver rollout to Recreate and pin bounded-readyz image
RollingUpdate maxSurge cannot schedule a second 50m pod on a node
packed to 99% CPU requests. Recreate replaces in place; the Service
already has no ready endpoints.
Image sha256:ec15f63d… is commit bc3d80f. Local release check passed
against disposable Postgres. No schema migration. Live Ready still
depends on a fresh runtime lease from ESO/OpenBao.
Assistant: grok
Assistant-Session: 01a0a182-bab7-7f11-b32b-d06f3af52082
This commit is contained in:
parent
bc3d80fbd9
commit
cf8c740b1b
4 changed files with 47 additions and 7 deletions
|
|
@ -8,7 +8,7 @@ the server port or export a copy before applying.
|
|||
Apply order is documented in `docs/operator-runbook.md`. Do not apply the
|
||||
Deployment until:
|
||||
|
||||
1. The image digest is pinned (currently `sha256:c2fe39a0…` from commit `abd22fa`).
|
||||
1. The image digest is pinned (currently `sha256:ec15f63d…` from commit `bc3d80f`).
|
||||
2. Secrets `audit-core-database`, `audit-core-database-migrate`, and
|
||||
`audit-core-senders` exist. ConfigMap `audit-core-senders-scope` is
|
||||
applied (`deploy/senders-scope.yaml`) before the Deployment mounts it.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue