Security

Twelve AI tools for Kubernetes compared, from open source troubleshooters to AI operations platforms and MCP servers, and how each one handles write access.

We turned a production OpenSearch stack into a reusable Ankra stack profile. The parameterisation exercise turned into an audit, and it found credentials that went nowhere, a security config that was never applied, and a retention policy pointed at every index in the cluster.

ingress-nginx is retired and its successor was cancelled before it shipped. A migration path to Gateway API that does not require a big-bang weekend.

Three weeks ago we called CVE scanners a layer-seven answer for teams who skipped the layer-one work. Then we shipped one. Here is why that is not a contradiction, and what a vulnerability finding has to become before it is worth anything.

A new name, a new engine, and the biggest release we have ever shipped: the Go rewrite, an AI that owns the incident loop, passkey security, European multi-cloud, and Ankra on your phone.

Half of all clusters are running an ingress controller that stopped receiving security patches in March. Meanwhile, teams debate service meshes. The five findings that show up in every real cluster security review, each with the incident that proves it and the fix.

Manage GitOps secrets by encrypting each value with SOPS and AGE before it reaches Git. Only ciphertext is committed and decrypted at deploy time.