Tales from the Crypt: Application Packaging and Delivery Nightmares
summary
Helm charts often morph into unreadable template spaghetti that generate hundreds of YAML files and require chart-specific expertise; conservative advice is to inventory actual app needs before converting to artifacts. Porter packages apps as OCI artifacts and Porter bundles CNAB get unwrapped then deployed — an anti-pattern seen at a multi‑billion dollar shop. Practical fixes include chart simplification (even breaking changes) and using a Helm post-renderer to patch rendered manifests while still deploying with Helm.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:26Talk structure
- 2:13What Helm is
- 4:59Helm chart complexity
- 7:11Porter as package manager
- 8:37Abusing Helm
- 10:01Analyzing Helm chart for engine X
- 12:06Kubernetes config categories
- 13:51Helm strengths
- 14:53Porter’s CNAB horror
- 16:17Five tips for tools
- 19:05Be chaos engineer
- 20:28Simple Helm charts
- 21:10Helm post-renderers
- 22:15Closing remarks
related talks
27mDay 2 Operations of Helm Charts
43mAt The Helm of Kubernetes: Repeatable Infrastructure Creation for Mere Mortals
29mHelm Chart Patterns
05mLightning Talk: New Helm Chart Installation Experience with Visual and Repeatable...
10mUsing Helm to the Fullest
07mLightning Talk: Merging Best Practices with Reality: One Repository for Code and Helm
34mOne Chart to Rule Them All: Continuous Deployment with Helm at Ticketmaster
26mHelm your way with Kubernetes