November 30, 2019

213 words 1 min read

One Chart to Rule Them All: Continuous Deployment with Helm at Ticketmaster

One Chart to Rule Them All: Continuous Deployment with Helm at Ticketmaster

As Kubernetes continues to mature, it's increasingly hard for users to keep track of the latest resource types, much less the best way to employ them. ReplicationControllers and Services were easy eno …

Talk Title One Chart to Rule Them All: Continuous Deployment with Helm at Ticketmaster
Speakers Raphael Deem, Michael Goodness (Lead Systems Engineer, Kubernauts, Ticketmaster)
Conference KubeCon + CloudNativeCon North America
Conf Tag
Location Austin, TX, United States
Date Dec 4- 8, 2017
URL Talk Page
Slides Talk Slides
Video

As Kubernetes continues to mature, it’s increasingly hard for users to keep track of the latest resource types, much less the best way to employ them. ReplicationControllers and Services were easy enough. Then came Deployments and Ingresses. Now we have PodDisruptionBudgets, ClusterRoleBindings, and HorizontalPodAutoscalers. Luckily, we also have Helm to package and deploy these various components (and more) as a single unit. In this talk we’ll dissect the single, flexible Helm chart Ticketmaster developed for use by multiple product teams. We’ll show how we use just a handful of variables to enable log collection with Fluentd, metric scraping with Prometheus, and automatic scaling of pods. Then we’ll demonstrate the GitLab CI workflow through which we deploy multiple builds of an application to multiple Kubernetes clusters running both on-prem and in AWS.

comments powered by Disqus