TGViewer
Kubesploit Kubesploit @kubesploit · 2.13K subscribers
Post #1587 1.07K
This article explores why using Kubernetes namespaces alone is not a sufficient isolation or security boundary.

It shows common pitfalls and many attack paths that let a tenant escape isolation even if you only gave them access to a single namespace.

More: https://ku.bz/PCmRjmB57
Open in Telegram All posts from @kubesploit
More from @kubesploit
  1. Sep 28, 2026Heading to KubeCon + CloudNativeCon North America? Join us the day before for our first in…
  2. Sep 25, 2026This tutorial builds a Docker image with a secret, then shows how it still sits in an earl…
  3. Sep 24, 2026This article explains how Vault piles up unexpired leases when pods keep re-authenticating…
  4. Sep 23, 2026This article asks what a container can block on its own when a dependency turns malicious,…
  5. Sep 23, 2026This week on Learn Kubernetes Weekly 202: 🔥 We Replaced etcd with Google Cloud Spanner 😌…
  6. Sep 22, 2026This article explains what an attacker can really do with leaked Kubernetes credentials, f…
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 →