talks to
summary
Experience deploying Java microservices in Docker and Kubernetes shows the JVM not container-aware problem causes the JVM to read host resources instead of cgroup memory limits, leading to JVMs OOMing, restarting and unstable pods on older Java. Upgrading to recent Java 8 updates and Java 12–14 reduces issues; community work adds container-aware GC ergonomics, container metrics, Java Flight Recorder and jcmd improvements. Try Google’s jib for image builds and test Project Portola on nonproduction clusters.
AI-written summary · about
