Lessons Learned from Maintaining Our Own Chart Repository
summary
Bitnami maintains 50+ charts split between the stable repo and a private repo and runs a Jenkins pipeline that builds images and charts, runs helm lint, helm install, verification tests (files, permissions, DB CRUD) and full functional UI tests that capture screenshots. Charts live on S3/ChartMuseum/Harbor; Harbor adds image CV scanning and signing. Deployment testing targets multiple cloud Kubernetes offerings and reveals storage and security-context issues resolved with init containers; the team adds upgrade tests with data persistence to guarantee safe in-place updates.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:53Four Main Points That You Will Need To Solve in Order To Have Your Repository Maintained
- 3:58Requirements for Storing Charts
- 5:22Testing
- 13:17Deploy to Several Clusters
- 17:09Other Tips
related talks
34mOne Chart to Rule Them All: Continuous Deployment with Helm at Ticketmaster
29mHelm Chart Patterns
32mManaging Helm Deployments with Gitops at CERN
06mFrom Enterprise Image Registry to Chart Repository
27mAre you Helming it the right way? Helm challenges and its solutions
05mLightning Talk: New Helm Chart Installation Experience with Visual and Repeatable App...
05mLightning Talk: New Helm Chart Installation Experience with Visual and Repeatable...
35mOptimizing Kubernetes Deployments with Helm
