Managing Apps Dependencies and Kubernetes Versions with Kraan and Flux
summary
Kraan is a Kubernetes controller that uses Flux’s source-controller and helm-controller to pull Helm charts from Git and reconcile cluster state, enforcing ordered installs via a prerequisites section and automatic retries. It implements a versioned layer dependency system so layer X waits for layer Y v2 (example: cert-manager v1→v2) before upgrading, avoiding breakages. It supports moving an addon between layers without reinstall via an orphan-and-adopt grace period and exposes Git-tracked layers and versions for cluster administrators.
AI-written summary · about
chapters (6)
- 0:00Intro
- 2:46Why use Crown
- 6:51Technical details
- 8:52Git repository reconciliation
- 11:39Business logic of Kraan
- 18:54Outro
related talks
38mAutomated & Observable Deployments with Flux + Keptn
47mOne Repo to Rule Them All: Kubernetes Cluster Tenancy with Flux v2
39mEnhance Your Kubernetes Experience with GitOps & Flux
27mHow DoD Uses K8s & Flux to Achieve Compliance & Deployment Consistency
01h 01mManaging Kubernetes the GitOps way with Flux- 38mAutomated & Observable Deployments with Flux + Keptn
36mManaging Thousands of Clusters and Their Workloads with Flux
40mTreating Kubernetes as a Linux Distro: APT-Style Packaging with FluxCD