...and here’s how to fix it
At kapitan.dev we believe the current way to manage Kubernetes configurations is broken. Actually, it probably goes even deeper than that, and you will see soon why.
I have a strange way to look at Kubernetes: for me Kubernetes is something that allows me…
So the other day using the Twitter @kapitandev handler I set the following challenge
Didn’t get many answers (help us! Please follow, RT and like) but I think many missed the point of the challenge. Good, because I have the right chance to talk about a hidden gem of…
In this post I would like to compare different ways to manage secrets in code, especially relevant to Kubernetes but also in general with a more broad reach.
UPDATE: Generators have been ported from
We open sourced Kapitan back in October 2017.
In the 12 months before that date, Kapitan helped us revolutionise the way we were running things at DeepMind Health, and allowed us to keep control over many heterogeneous systems: Kubernetes, Terraform…
Efficiently managing secrets is an essential part of any configuration management tool that cannot be left to the last minute. When evaluating a solution for Kapitan, we immediately looked into plug-in solutions like the amazing git-crypt which was at the time one of the suggested approaches for Helm.
In my previous posts, I explained the basic of Kapitan and how it can be used to drive complex deployments of Kubernetes. This post will pick up where we left off on the Introduction to Kapitan, and go more into details on how to use jsonnet to manage Kubernetes configurations.
In my first post I explained a little bit the philosophy behind Kapitan and how it came to be.
In this post, I will give a more pragmatic introduction so that you can easily evaluate it and see if it fits your needs.
Kapitan is a tool to template files…
This story is all about Kapitan, the tool that will help you manage your Kubernetes configuration and make you feel good about it.