An introduction to Helm - KubeCon EU 2020
- 2. @bridgetkromhout @marckhouzam#kubecon Bridget Kromhout Marc Khouzam
- 3. @bridgetkromhout @marckhouzam#kubecon 1.Overview: fundamental concepts 2.Getting started with charts 3.Migrating from v2 to v3 4.Community
- 6. @bridgetkromhout @marckhouzam#kubecon Find, share, and use software built for k8s Manage complexity Easy updates Simple sharing Rollbacks
- 7. @bridgetkromhout @marckhouzam#kubecon demo: getting started with Helm
- 8. @bridgetkromhout @marckhouzam#kubecon Finding charts decentralized search & repo addition hub.helm.sh artifacthub.io and more…
- 10. @bridgetkromhout @marckhouzam#kubecon Customizing and making charts: helm.sh/docs/chart_template_guide/getting_started/
- 11. @bridgetkromhout @marckhouzam#kubecon Why Helm v3? - v3 based on community best practices - dramatic simplification of architecture - security and production use as priorities
- 12. @bridgetkromhout @marckhouzam#kubecon Helm v3 replacing v2 - bugfixes for v2 have ended - security patches end in November 2020
- 13. @bridgetkromhout @marckhouzam#kubecon what’s different in Helm v3? - using Kubernetes API server instead of Helm’s own custom server (Tiller) - making Helm more k8s-native - inheriting security controls from kubeconfig - using k8s RBAC to limit access & resources
- 14. @bridgetkromhout @marckhouzam#kubecon --generate-name - old style: auto-generated unless overridden - new style: error unless auto-generation requested
- 15. @bridgetkromhout @marckhouzam#kubecon library chart support - shared by other charts - does not create any release artifacts of its own - a library chart’s templates can only declare “define” elements - allows simpler code reuse
- 16. @bridgetkromhout @marckhouzam#kubecon farewell, Tiller - simpler & more flexible architecture, security, & upgrades - now using Kubernetes API directly - rendering Charts client-side; storing in release - lowering the barrier of entry for contributors
- 17. @bridgetkromhout @marckhouzam#kubecon upgrade vs convert - we now default to the same namespace for a release and objects (no longer using the Tiller namespace) - can’t upgrade a Helm v2 release with Helm v3 (but you can convert it with helm-2to3, then upgrade)
- 19. @bridgetkromhout @marckhouzam#kubecon what did we just see? - Helm v3 cannot see Helm v2 resources - if you just update from v2 to v3 and do nothing else, it will seem like everything is missing! - essential to migrate and convert as applicable
- 20. @bridgetkromhout @marckhouzam#kubecon tl;dr: Make sure you’re using Helm 3 today. We’re here to help! helm.sh/docs/faq/ cncf.io/webinars/a-conversation-about-helm-3/ cncf.io/webinars/cncf-project-webinar-charting-your- voyage-to-helm-3/
- 21. @bridgetkromhout @marckhouzam#kubecon Community! - helm.sh/docs (contributions welcome!) - github.com/helm/helm (issues, PRs, learning!) - github.com/helm/community (Twitter, Slack, mailing lists, weekly call)