The HA pod was OOMKilled (exit 137) on 2026-07-09 20:48:46 against the 8Gi limit.
The 8Gi ceiling dates from when HA ran on the 12Gi k8s-edge VM. It now schedules on the general pool, where nodes have ~47Gi allocatable, so there is no reason to keep it below the 16Gi the legacy HAOS VM gave this workload.
Scope: memory limit only. The roborock/dreame_vacuum/dwd_weather setup failures seen after that OOMKill are a separate upstream cffi issue and are deliberately not addressed here.
Generated with Claude Code
The HA pod was OOMKilled (exit 137) on 2026-07-09 20:48:46 against the 8Gi limit.
The 8Gi ceiling dates from when HA ran on the 12Gi k8s-edge VM. It now schedules on the general pool, where nodes have ~47Gi allocatable, so there is no reason to keep it below the 16Gi the legacy HAOS VM gave this workload.
Scope: memory limit only. The roborock/dreame_vacuum/dwd_weather setup failures seen after that OOMKill are a separate upstream cffi issue and are deliberately not addressed here.
Generated with Claude Code
The pod was OOMKilled (exit 137) on 2026-07-09 20:48:46 against the 8Gi
limit. The 8Gi ceiling dates from when HA ran on the 12Gi k8s-edge VM;
it now schedules on the general pool, where the nodes have ~47Gi, so
there is no reason to keep it below the 16Gi the HAOS VM used to give
this workload.
The restart that OOMKill caused also broke roborock, dreame_vacuum and
dwd_weather: a fresh container re-runs HA's uv-based requirement install,
which upgraded cffi 2.0.0 -> 2.1.0 on disk after _cffi_backend 2.0.0 had
already been imported, and every pycryptodome-backed integration then
died on the resulting FFI version mismatch.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
The HA pod was OOMKilled (exit 137) on 2026-07-09 20:48:46 against the 8Gi limit.
The 8Gi ceiling dates from when HA ran on the 12Gi k8s-edge VM. It now schedules on the general pool, where nodes have ~47Gi allocatable, so there is no reason to keep it below the 16Gi the legacy HAOS VM gave this workload.
Scope: memory limit only. The roborock/dreame_vacuum/dwd_weather setup failures seen after that OOMKill are a separate upstream cffi issue and are deliberately not addressed here.
Generated with Claude Code