Insights, tutorials, and thoughts on modern DevOps, Kubernetes, and cloud-native technologies.
Subscribe via RSSHalf 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.
Every GitOps rollout stalls on one question: where do the secrets go? A practical guide to SOPS and AGE encryption in Ankra, so credentials live in Git safely and AI-generated config never leaks a key.
On June 15, Hetzner raised cloud prices, with some instance families more than doubling. A worked-numbers look at what a production Kubernetes cluster costs now, and why the real lesson is portability, not provider loyalty.
Spectro Cloud's Palette is a serious enterprise platform for provisioning Kubernetes estates from the OS up. Ankra is an AI-native platform for running everything that happens on Kubernetes from the app down. The honest comparison, including when Palette is the right call.
New Ankra clusters no longer run ArgoCD. Here is the engineering story of the native deployment engine: why we built it, how the reconcile loop works, what the migration does to your live resources (nothing), and what we have not finished yet.
Prometheus is the right first monitoring stack for almost everyone, and the wrong last one for a growing minority. An honest comparison of the two, the cardinality wall that forces the question, and how to run either (or both) on Ankra.
Every logging decision is secretly one question: how much of your log data do you index? A working comparison of Elasticsearch, OpenSearch, Grafana Loki, and cloud services like GCP Logs Explorer, with real pricing math and a decision framework.
'Don't use Kubernetes until you have a platform team' was good advice in 2019. The premises changed. What a two-to-six person company should set up in week one, what to deliberately skip, and what it actually costs: about zero.
A practical guide to wiring an infrastructure agent into your CI: review comments on pull requests, deploy verification on merge, and Slack reports that contain an actual root cause instead of a red X.
Cursor is good at application code but loses context the moment a change crosses into Kubernetes, Helm, and CD pipelines. Adding the Ankra CLI as an infrastructure subagent gives it cluster-aware grounding so developers and platform teams can work on the same artifacts.