Adjusting your spyglass & looking out over the water, you can see how useful a package manager like Helm is. Perhaps you’ve used it to manage the fractal complexity of packages on your Kubernetes clusters (without losing track of versions stashed in the hold). But Helm 3 is rumored to be different; you’re ready to get started on this exciting voyage as soon as you have some idea of what’s port & what’s starboard!
Get clear answers to questions like “when do I use Go templates versus Lua?”, “how do I move my production Helm 2 installation to Helm 3 seamlessly?”, “what do I use now instead of tiller?” In this demo-fueled session, we’ll take you through differences from the Helm of yore, tips for a successful rollout or upgrade, & opportunities to shape the project’s future. The cloud native waters can be choppy but a technical deep dive powered by open source tooling will steer you right!
1. You are free to disagree. 2. I disagree with bashing companies for past mistakes when good is being done, made, and had. 3. I can’t reply anymore because I’m going to be part of that good and deliver another OSS session on Helm3 at #KubeconEU. pic.twitter.com/fcZS0y0bJk
Helm has been evolving since the inception of Kubernetes. With Helm 3, we are catching up and making use of native primitives and security conceptsthat are now available. #Kubeconpic.twitter.com/fuMrCGXKqi
helm3 is also onboarding some CLI Also, beware of breaking changes. You cannot upgrade a release from Helm2 to Helm3 on the same cluster right know if I got it right. You can't directly upgrade right now but something is being worked on regarding that! pic.twitter.com/1G5LZP0fLk
Reminder : Helm3 is currently still in alpha so people are welcome to contribute since things can change and will change. Lua will allow simplifying some charts instead of using go templates. Sometimes having a full language makes things easier (what about the added complexity?)
So about the demo... A lot of people are wondering how it will operate without Tiller... Simple: the same way! Helm2 will complain of Tiller absence but things will work like before. pic.twitter.com/FGsCAHLxEi
Multiple Helm versions cohabitation : "We should warn you, this is not an actually recommended production setup #disclaimer " Featuring kubens (I think everyone is already using it or people lives have to be a nightmare)
If you're super interested in tillerless #Helm, you can check out the Helm 3 alpha1 now! Check out what's coming in the alphas and check them out so you can give feedback to make sure the Helm 3 release will work for you! #KubeCon#CloudNativeConpic.twitter.com/WHL3vBNBkm
Demo end 😢 Back to the presentation with different Helm3 alpha releases Reminder : Feedback will be a huge part of the evolutions of Helm so go and try Helm3, give feedback, talk with people, contribute documentation, share your usecases, ... 💡 Get involved! ⚡ pic.twitter.com/CFRMkWGdqI
And that will be it for today - except if you go to the Deep Dive on Helm later today at #Kubecon#cloudnativecon ofc 😉 First time trying to cover a talk with a live tweet thread, probably did it badly, but looked like it could be useful anyway! Hope you'll give Helm3 a try 😁
@jldeen Great to hear about @HelmPack v3 release, awesome catchup. I thought it would be useful to isolate the Helm 3 binary into a container to segregate different version configuration. Might be useful 🤷🏼♂️ https://t.co/MY1b1HUn9I. #KubeCon