BestHub
Sign in
dbaplus Community
dbaplus Community
Aug 18, 2025 · Cloud Native

Why Ubuntu 22.04 Upgrade Crashes Java Apps on Kubernetes: The cgroup v2 Trap

Upgrading a Kubernetes cluster from CentOS 7.9 to Ubuntu 22.04 caused Java pods to crash with OOMKilled errors; increasing memory limits only hid the issue, and the root cause was cgroup v2 making the JVM misinterpret its resource limits, resulting in excessive threads and heap sizes. The article advises upgrading to a JVM that supports cgroup v2 or reverting the node to cgroup v1.

JVMJavaKubernetes
0 likes · 8 min read
Why Ubuntu 22.04 Upgrade Crashes Java Apps on Kubernetes: The cgroup v2 Trap
DevOps Cloud Academy
DevOps Cloud Academy
Dec 11, 2023 · Operations

Managing Java Process Memory in Kubernetes Pods to Prevent OOMKilled

This article explains why Java processes in Kubernetes pods often encounter OOMKilled despite correct JVM heap settings, analyzes the discrepancy between JVM‑reported memory and container metrics, and provides practical steps such as adjusting MaxRAMPercentage and pod memory limits to stabilize memory usage.

JVMJavaKubernetes
0 likes · 9 min read
Managing Java Process Memory in Kubernetes Pods to Prevent OOMKilled
Efficient Ops
Efficient Ops
May 22, 2023 · Operations

Fix Common Kubernetes Errors: ImagePullBackOff, CrashLoopBackOff & More

This guide walks operators and developers through diagnosing and resolving frequent Kubernetes issues such as ImagePullBackOff, CrashLoopBackOff, OOMKilled, BackoffLimitExceeded, and probe failures, providing key kubectl commands, secret handling tips, and best‑practice recommendations to keep clusters stable.

CrashLoopBackOffImagePullBackOffKubernetes
0 likes · 11 min read
Fix Common Kubernetes Errors: ImagePullBackOff, CrashLoopBackOff & More
Open Source Linux
Open Source Linux
Jan 17, 2023 · Backend Development

Why Your Java App Gets OOMKilled in Kubernetes and How to Fix It

This article explains why Java applications running in Kubernetes containers are often terminated with OOMKilled (exit code 137), analyzes the underlying JVM memory‑limit mismatches, and provides practical solutions using cgroup‑aware JVM flags and memory‑tuning techniques.

DockerJVMJava
0 likes · 14 min read
Why Your Java App Gets OOMKilled in Kubernetes and How to Fix It