Beyond Namespaces: Why Kubernetes Needs Real Workload Isolation | Dark Hacker News