K-L4 · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
Kill a server pod mid-delivery, drain a node, fail over the PostgreSQL primary, restart NATS, 60 s S3 outage. No message lost or duplicated.
Done when
All scenarios green in CI or nightly
Depends on: K-L2
**K-L4** · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
Kill a server pod mid-delivery, drain a node, fail over the PostgreSQL primary, restart NATS, 60 s S3 outage. No message lost or duplicated.
**Done when**
- All scenarios green in CI or nightly
**Depends on:** K-L2
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 05:14:46 +00:00
Done: #35 merged. All five scenarios green on the bench and in CI (run 44692133063: chaos on 1.37, amd64 and arm64); nightly from now on.
Done: #35 merged. All five scenarios green on the bench and in CI ([run 44692133063](https://github.com/inbuxa/inbuxa-k8s-lab/actions/runs/44692133063): chaos on 1.37, amd64 and arm64); nightly from now on.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
K-L4 · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
Kill a server pod mid-delivery, drain a node, fail over the PostgreSQL primary, restart NATS, 60 s S3 outage. No message lost or duplicated.
Done when
Depends on: K-L2
Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.
Started: #35.
Done: #35 merged. All five scenarios green on the bench and in CI (run 44692133063: chaos on 1.37, amd64 and arm64); nightly from now on.