TGViewer
Kubesploit Kubesploit @kubesploit · 2.13K subscribers
Post #1709 340

Forwarded from KubeFM

Nicholaos Mouzourakis, Staff Product Security Engineer at Gusto, explains a fascinating performance issue they encountered when deploying Open Policy Agent in Kubernetes. He details how Go's default thread management clashed with Kubernetes CPU resource limits, causing significant performance degradation.

The core issue: Go automatically spawns threads equal to the number of CPU cores reported by the OS (8 in their case), but Kubernetes with a 750 millicore limit only allowed access to 75% of a single core. This meant all 8 Go threads were competing for limited CPU resources, creating what he describes as "context switch thrashing."

Nicholaos shares how they diagnosed this problem and the counterintuitive solution - reducing GOMAXPROCS from 8 to 2 - which immediately improved performance.

Watch the full episode: https://kube.fmhttps://ku.bz/S-2vQ_j-4
More from @kubesploit
  1. Sep 25, 2026This tutorial builds a Docker image with a secret, then shows how it still sits in an earl…
  2. Sep 24, 2026This article explains how Vault piles up unexpired leases when pods keep re-authenticating…
  3. Sep 23, 2026This article asks what a container can block on its own when a dependency turns malicious,…
  4. Sep 23, 2026This week on Learn Kubernetes Weekly 202: 🔥 We Replaced etcd with Google Cloud Spanner 😌…
  5. Sep 22, 2026This article explains what an attacker can really do with leaked Kubernetes credentials, f…
  6. Sep 22, 2026"When an agent goes loose, you might find yourself: your S3 bucket has been deleted by mis…
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →