CRE-2025-0119
During rolling updates, when a deployment's maxUnavailable setting conflicts with
During rolling updates, when a deployment's maxUnavailable setting conflicts with
Exit code 127 indicates the configured command/entrypoint was not found in the image or PATH.
Exit code 134 indicates the process aborted via SIGABRT, commonly due to failed assertions,
The container exceeded its memory limit and was killed by the kernel OOM killer.
Exit code 139 indicates SIGSEGV (invalid memory access) in native/runtime code.