Verwaltet von:
I’ve been giving #kapitan a shot these days. So far I only have good words about this “advanced #configuration #management” tool! Everything is absolutely modular and you have full control on how you’d like to structure the things.
What do you need? Automatic generation of docs? You got it, throw in a template (Jinja2, Kadet, Jsonnet), put it in your inventory and you’ll be amazed of unlimited power.
#Helm support is built-in. Ever wanted to guard yourself from 
upstream fuckups without having to pull the chart in your registry and hacking it? Well, guess what, you can tackle this with kapitan.
Community-wise: I’ve just dropped a line in their Slack channel when I initially started and the lead maintainer offered to give me some recommendations on how I could structure the whole thing; I’ve been onboarded in no-time and had my first project deployed to production in less than 30m.
My background: I was trying to rollout a Production & Staging
@dminca@mastodontech.deGitLab stack on #Kubernetes on-prem. Started initially with #FluxCD but it all got messy in no-time. #SealedSecrets being pushed in 2 clusters, configuration drifts between environments popped-up and suddenly it all gone out of control. #GitLab recommends deploying external PostgreSQL, MinIO and Redis clusters for production, Bitnami helm charts are so far the best choices here.
Decided to move all that stuff to kapitan and suddenly all those problems vanished.
You wrap everything into
your CI/CD tool of choice, write an air-gapped and robust pipeline and you’ve finally got yourself an assembly line.
If you’re just new to kapitan or simply curious and wanna try it out, you can drop a line on their Slack, 100% someone will be there for you, community’s great 