Go is not aware of the limits set for its container, causing some issues not easy to track. This is a story about how I stumbled into one of them.

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

This post explores an issue encountered when using Kubernetes and Go together, where the Go program is not aware of the resource limits set for its container. The post explains how the issue manifests, provides insights into Go's garbage collector, and suggests a solution using the GOMEMLIMIT environment variable.

When Kubernetes and Go don't work well together

Permalink As Monk would say, here’s what happened…

Permalink Hunches are fine, but show me the facts

<p>Yep, I had experienced this. Just like Node.js that doens’t work smoothly either.</p>
