TGViewer
Kubesploit Kubesploit @kubesploit · 2.13K subscribers
Post #1748 179

Forwarded from KubeFM

Brian Stack from Render explains why Kubernetes scaling can break along a dimension most teams ignore: namespaces.

At Render scale, hundreds of thousands of namespaces made common DaemonSet patterns expensive. Calico and Vector were list-watching namespace data across every node, multiplying memory usage and putting pressure on the API server during restarts and rollouts.

You will learn:

- Why namespaces can become a hidden scaling bottleneck
- How DaemonSets multiply memory and control-plane pressure
- How profiling, staging clusters, and upstream collaboration freed 7 TiB
- Why pushing from an 80% fix to a complete fix can make teams faster

Watch (or listen to) it here: https://ku.bz/0mrvCsXrV

🌟 This episode is brought to you by LearnKube — comprehensive Kubernetes training. https://learnkube.com/training

With @Birthmarkb
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 →