How Honestbee does CI/CD on Kubernetes
summary
Honestbee runs Kubernetes in production since mid 2016 and uses Helm + Drone.io to render templates and drive CI/CD, with Helm values committed as the canonical cluster definition. Secrets live in Vault via VaultController or encrypted with Mozilla sops and managed with helmfile. Chart repositories run on S3 and ChartMuseum after a few iterations. Dashboards and Terraform are generated from Helm values, and auto-deploy uses Keel; the migrations and tooling work in production.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:17What is Honestbee?
- 1:38What is Swat?
- 2:06Overview
- 2:31What are Containers?
- 4:57Why Containers?
- 7:34More than just packaging and Isolation
- 9:54Star Trek?
- 11:46Version 1: sed
- 12:28Version 2: jinja
- 14:20Different requirements
- 15:02Kubernetes Deployment challenges
- 16:36Chart, Repositories, Releases
- 17:30Helm Charts
- 18:21Easy to manage deployments
- 19:05Tip: Labels
- 21:27Tip: Powerful templating
- 23:13Tip: Automate monitoring / alerts
- 23:46Tip: Helm Values
- 25:40Private Chart Repository
- 27:19Secrets?
- 32:49Swat: Secrets
- 36:06Swat - Pluggable CD
related talks
35mOptimizing Kubernetes Deployments with Helm
26mHelm your way with Kubernetes
35mLearn About Helm And Its Ecosystem
36mDelve into Helm: Advanced DevOps [I]
22mCreating a Micro Open-Source Community with Helm
41mHelm - the Better Way to Deploy on Kubernetes
32mHelm your way with Kubernetes
28mShip It Faster, Safer & Cheaper GitOps with Helm