Kaur Kallas
Kaur Kallas is the founder of Sparky Solutions, an independent DevOps, Platform Engineering and SRE consultancy based in Tallinn, Estonia. Estonia’s first CNCF Kubestronaut and a certified AWS and Google Cloud architect, he helps everyone from startups to regulated banking and health-tech enterprises adopt cloud-native architecture, Infrastructure as Code, and zero-trust DevSecOps practices that hold up in production — across multi-cloud, hybrid and on-prem, including bare-metal Kubernetes on Talos, with Argo CD, Kargo and Crossplane.
AI in the CI/CD loop: let the gates do the trusting
AI coding agents are good enough now that writing the code is no longer the bottleneck — trusting what gets shipped is. “It compiles” and “it looks right to the model” are not quality gates. If you let an agent merge and deploy on its own judgement, you’ve quietly replaced code review and testing with vibes. The fix isn’t to keep AI out of production. It’s to make it pass exactly the same gates a human would.
Read MoreYour IDP is the face of your organisation, not a scaffolding tool
Internal Developer Platforms — Backstage being the obvious one — usually get sold on bootstrapping: click a template, scaffold a new service, get a repo with CI already wired up. That’s a nice party trick. It’s also the least interesting thing an IDP does, because you scaffold a service maybe a handful of times a year.
Read More
From commit to production: how Kargo completes the GitOps flow
Most teams that adopt GitOps end up with two-thirds of a delivery pipeline. CI builds and pushes an image. Argo CD reconciles the cluster to whatever is declared in Git. Both halves are solid. But the bit in the middle — moving a change through dev, staging and production, with checks at each step — is almost always a pile of bespoke scripts, manual pull requests, and “just bump the tag in the prod values file.” That’s where Kargo comes in.
Read MoreZero-code observability: OpenTelemetry meets eBPF with OBI
OpenTelemetry has more or less won the observability standard war, and for good reason — vendor-neutral traces, metrics and logs, one wire format (OTLP), one collector to ship it all wherever you want. The catch is the part nobody enjoys: actually instrumenting the code. SDKs mean touching every service, in every language, and redeploying. For a greenfield Go service that’s fine. For forty mixed-language services — half of which nobody wants to redeploy — it’s a project.
Read MoreBecoming Estonia's first Kubestronaut
A while back I became the first CNCF Kubestronaut in Estonia. The jacket is nice, but the reason I went after it is more practical: the program is a genuinely good map of what it takes to run Kubernetes well, end to end.
Read MoreA local Argo CD playground with kind
The fastest way to build confidence in a GitOps change is to run it somewhere disposable first. I keep a local Argo CD stack on kind (Kubernetes in Docker) for exactly that — a cluster I can create, break, and throw away in minutes.
Read MoreGitOps your cloud infrastructure with Crossplane and Argo CD
Most teams already deploy their applications with GitOps: the desired state lives in Git, and a controller like Argo CD reconciles the cluster to match. So why is the infrastructure underneath those apps still provisioned by someone running Terraform from a laptop — or worse, clicking around a cloud console at 2am?
Read More