Understanding Kubernetes Exit Code 137: A Silent-killer of Java apps

At Moss, Java apps are<a href="https://medium.com/mossfinance/tech-at-moss-the-b2b-spend-management-platform-21cda1a76c12" rel="noopener"> at the core of our microservices</a>. However, from time to time, they encounter issues. This is where the Moss Platform Team steps in. We are the team responsible for ensuring the smooth operation of applications on Kubernetes. A few weeks ago, an issue occurred when some of our microservice pods began restarting unexpectedly, without any apparent reason and at varying hours. It became clear that something was wrong. Our <a href="https://cloud.google.com/blog/products/devops-sre/sre-fundamentals-slis-slas-and-slos" rel="noopener ugc nofollow" target="_blank">Service Level Objectives</a> (SLOs) remained intact, thanks to the multiple redundancy layers in place for our workloads. However, our monitoring systems showed that certain pods were undergoing restarts. <a href="https://medium.com/mossfinance/understanding-kubernetes-exit-code-137-a-silent-killer-of-java-apps-b4015ee128e1">Read More</a>