Helm Yeah! How Helm Came to Be
At its core, Helm was built to help with two things.First, Helm wants to make it simple to share information about running apps and services inside of Kubernetes. When the community all share our char …
Talk Title | Helm Yeah! How Helm Came to Be |
Speakers | Matt Fisher (Software Engineer, Microsoft) |
Conference | Open Source Summit North America |
Conf Tag | |
Location | Vancouver, BC, Canada |
Date | Aug 27-31, 2018 |
URL | Talk Page |
Slides | Talk Slides |
Video | |
At its core, Helm was built to help with two things.First, Helm wants to make it simple to share information about running apps and services inside of Kubernetes. When the community all share our charts, the Kubernetes community at large learns how best to work with Kubernetes. We share information and discover great ways of doing things. And we also make it easier for newcomers to get going. Helm is about growing Kubernetes.Second, Helm wants to make it easier for teams to manage their Kubernetes manifest files. The Helm community created a tool that eases the process of collaborating on and keeping track of your team’s charts. Start with widely available charts, customize them to your team’s needs, and then store them in your own version control. Helm is about helping teams.Kubernetes is a powerful platform. Helm was built to make it easy to manage the apps and services you deploy.In this session, we’ll explore the history of Helm, how Helm is used today, share useful tips and tricks the community has developed, and how to get involved in the Helm community. We’ll also share some of the worst puns the Helm community has to offer.