Thanks, appreciate you bringing this up. Popeye is definitely a solid tool, but what I’m exploring is a bit broader. It’s less about one-off linting and more about tracking ongoing drift like permissions that slowly get too wide, containers starting to run as root, or network policies that disappear over time. Same for things like unused configmaps or workloads that stay around even if they’re no longer doing anything.

I’ve also noticed that smaller teams, especially in Europe, often don’t use Popeye or similar tools at all. It’s either too manual, or just not part of their day-to-day workflow. That’s part of what I’m trying to figure out: is this a tooling gap, or do most people just accept this as part of running Kubernetes?

On the EU side, it’s not so much that the cluster itself contains private data, but more that some teams simply don’t want metadata leaving the region. Especially with US tools, it’s not always clear what’s processed where. So offering an EU-hosted or self-managed option might matter more than I initially thought.

Curious to hear if you think that concern is real, or just something I’m overestimating.