Tag: K8s

During rolling updates, when a deployment's maxUnavailable setting conflicts with a Pod Disruption Budget's minAvailable requirement, it can cause service outages by terminating too many pods simultaneously, violating the availability guarantees.This can also occur during node drains, cluster autoscaling, or maintenance operations.

Exit code 127 indicates the configured command/entrypoint was not found in the image or PATH.New or misconfigured deployments commonly hit this and immediately crash.

Exit code 134 indicates the process aborted via SIGABRT, commonly due to failed assertions,allocator checks (e.g., glibc detecting heap corruption), or explicit abort() calls.

The container exceeded its memory limit and was killed by the kernel OOM killer.Kubernetes reports a terminated state with Reason=OOMKilled and exitCode=137.This often manifests as CrashLoopBackOff under sustained memory pressure.

Exit code 139 indicates SIGSEGV (invalid memory access) in native/runtime code.Frequently caused by unsafe pointer operations, ABI/library mismatches, or native extensions.