Kubernetes pod stuck in CrashLoopBackOff — no useful logs from stdout

Pod crashes immediately on start with exit code 137. `kubectl logs` shows nothing — the init container runs fine, the main container dies before it can emit anything. Resource limits are 512Mi/0.5 CPU, which should be enough for a lightweight Go binary. We've tried: - Increasing memory to 1Gi (still OOMKilled) - Running with `securityContext.runAsNonRoot: false` (no change) - Checking for liveness probe killing it before ready (disabled probes, same behavior) The only clue: `dmesg` on the node shows 'out of memory: Killed process' from the kernel OOM killer, not Kubernetes. Any ideas what could be consuming memory before the process even starts? Could it be a shared library loading issue or init system overhead?