CRI-O
v1.34.9Kubernetes CoreCRI-O v1.34.9 fixes two concurrency bugs: a panic from racing StopContainer calls and a spurious exit code 255 on fast-exiting containers. Pure bug-fix release, no dependency changes.
breakingPanic risk on concurrent StopContainer — upgrade if you drain nodes or run rapid pod teardowns
If your cluster drains nodes, runs batch workloads with rapid pod churn, or uses any automation that issues multiple StopContainer calls in parallel, the pre-fix versions could panic CRI-O, taking down the container runtime on that node. This is a hard crash, not a graceful error. Upgrade to v1.34.9 immediately on any node where concurrent stop operations are plausible.
enhancementExit code 255 false positives are gone — review alerting and restart policies
Exit code 255 is often treated as a runtime-level failure in monitoring stacks and can trigger unnecessary pod restarts or alerts. If you have OOMKill or fast-exit workloads (init containers, short-lived jobs) and have seen spurious 255 exit codes in your logs or metrics, those were false positives from this race. After upgrading, audit your alerting rules and CrashLoopBackOff history — you may find some pods were incorrectly flagged.
主な変更 (3)
- Fixed panic caused by concurrent StopContainer calls sending on an already-closed channel
- Fixed race condition that incorrectly reported exit code 255 for containers that exited quickly
- No dependency additions, changes, or removals