Latest Posts
Claude Code: AI Agent for DevOps, SRE, and Platform Engineering
If you are a software engineer, you are probably already using an AI agent like GitHub Copilot, Cursor, Windsurf, Cline or something similar. If you are, you probably have an opinion which one of those is the best one out there. Or you might have been dissapointed with the results AI agents provide and chose to use none of them.
Today I’ll tell you which one is the best AI agent for any type of software engineers, especially for those focused on operations. If you call yourself DevOps, or SRE, or Platform Engineer, you’ll find out which one you should use.
Ready?
AWS Controllers for Kubernetes (ACK): Is It Worth It?
It’s not a secret that I believe in Kubernetes and that I think that it is much more than a “thingy where we run containers”. It is an extensible API with controllers that can manage any type of resources. It is a control plane for everything.
That’s why, a while ago, I was very excited when AWS Controllers for Kubernetes (ACK) project was born. It allows us to extend Kubernetes with Custom Resource Definitions and controllers that allow us to manage AWS resources through Kubernetes.
Kro vs Helm: Is It Time to Ditch Helm Charts?
During recent months I saw a lot of conversation and questions sparked by the release of kro, like the one in the picture. Many of them are related to comparison with Helm. Some people think that kro is, more or less, doing the same work as Helm. Others think that it is a different syntax that accomplishes the same result as Helm. Some are asking whether kro is a replacement for Helm.
There’s hardly a day that I don’t see a blog post or a Slack conversation or a question in Reddit around that subject.
I want to answer those questions today.
Mirrord Magic: Write Code Locally, See It Remotely!
Imagine this scenario.
There is a frontend application that talks to a backend which uses a database.
I am working on the code of that backend application.
I neither have nor care about the code of the frontend app and I do not have the database running locally. All I want is to write the code of that backend application and see the outcome of my work, either directly or through the frontend (the one that I am not running) and I want that local code to be connected to the database (which I am also not running).
Stop Using Docker and Local Kubernetes for Dev Environments! (feat. Okteto)
You are developing something. Everybody is, no matter whether that something is a user-facing application, infrastructure, or anything else.
While developing, you are trying to set up a development environment, probably locally since that’s where your code is. You are likely trying to do all that using Docker or a local Kubernetes cluster like KinD.
If that’s what you’re doing, I’m here to tell you that you’re doing it wrong.
Remote Environments with Dev Containers and Devpod: Are They Worth It?
Today we are going to explore running remote ephemeral development environments. We are going to see (potentially) the best solution you should (probably) NOT use. If that sounds confusing, you’re not alone.
We’ll explore the Development Containers spec as well as Devpod as an implementation of that spec. Together, they provide a way to run ephemeral development environments.
There is a hidden reason for going through those. I have serious doubts about the story behind remote environments, at least in a specific form, and I want to discuss what we really want them for. But, to do that, we need to go through a few practical examples to be on the same page before I go off the beaten path and start questioning it all.
Buckle up. You’re in for a ride that starts with some important questions that turn into excitement and finish… Well… I do not yet know how it will finish.