Don’t Read the Manual: Automating Helm Provisioning with Terraform
summary
Shows Terraform driving Helm by creating a GKE cluster and a Helm release that runs Vault, with Terraform changing 5→7 Vault pods and producing a new Helm revision; Helm stores the condensed release in a helm release stored in k8s secret, and Terraform uses the terraform manages helm_release resource to write values. Demo shows a manual helm upgrade that disables the Vault UI out of band; Terraform detects that drift but cannot automatically revert Helm-made changes.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:24Automating Helm Provisioning with Terraform
- 2:25Agenda
- 6:26Kubernetes Manifest Is Human Readable
- 10:45Terraform Binary
- 17:55Ci Defying Your Infrastructure as Code
- 18:49Out of Band Changes to the Infrastructure
- 28:44Helm Upgrade
related talks
23mManaging Vault with Terraform
23mSimplifying Kubernetes deployment with Terraform for OpenAI
43mAt The Helm of Kubernetes: Repeatable Infrastructure Creation for Mere Mortals
10mUsing Helm to the Fullest
41mHelm - the Better Way to Deploy on Kubernetes
32mHelm your way with Kubernetes
21mKubernetes, AWS, ALBs, Terraform and no Helm!
26mHelm your way with Kubernetes