---
title: "Comment by Amit Malhotra on \"Anything can talk to anything: the Kubernetes default quietly expanding your blast radius\" | Hashnode"
description: "This is one of those Kubernetes topics that's easy to underestimate. One thing I've seen repeatedly is that many teams assume namespaces provide meaningful isol"
url: "https://hashnode.com/posts/anything-can-talk-to-anything-the-kubernetes-default-quietly-expanding-your-blast-radius/6a6a7661d589bd8a6fdb7e71/comment/6a6ac92e75fce62ae42fee0e"
---

[Discussion](https://hashnode.com/posts/anything-can-talk-to-anything-the-kubernetes-default-quietly-expanding-your-blast-radius/6a6a7661d589bd8a6fdb7e71)

Comment [Anything can talk to anything: the Kubernetes default quietly expanding your blast radius](https://hashnode.com/posts/anything-can-talk-to-anything-the-kubernetes-default-quietly-expanding-your-blast-radius/6a6a7661d589bd8a6fdb7e71)

[Amit Malhotra](https://hashnode.com/@vertro-io)

[Jul 30](https://hashnode.com/posts/anything-can-talk-to-anything-the-kubernetes-default-quietly-expanding-your-blast-radius/6a6a7661d589bd8a6fdb7e71/comment/6a6ac92e75fce62ae42fee0e)

This is one of those Kubernetes topics that's easy to underestimate. One thing I've seen repeatedly is that many teams assume namespaces provide meaningful isolation, when in reality they're often just an organizational boundary. The real blast radius is determined by the combination of NetworkPolicies, RBAC, service accounts, admission controls, and workload identity—not namespaces alone. Security by default should be about reducing the reachable surface, not just segmenting resources. A timely reminder that Kubernetes defaults are designed for flexibility, not least privilege.