liveBook · Manning

Helm chart

As explained in Machine Learning Platform Engineering

A Helm chart is a packaged collection of Kubernetes resource templates and configuration values used to define an application deployment.

A Helm chart packages the Kubernetes objects needed by an application so they can be installed and maintained together. It combines YAML object templates with configurable values, typically stored in values.yaml. A template can obtain a Service type or port from that file; a Deployment can obtain an image name or resource requests. This avoids editing each object file separately for routine changes. section 3.3.6

Figure 3.9 The service_template.yaml file defines the K8s service, and the type of service and port are obtained from values.yaml. The template and values form the core of a Helm chart.
A screenshot of a computer

AI-generated content may be incorrect.

The Service template and values.yaml show the core relationship: the template defines the Kubernetes object, while values supply its customizable properties. section 3.3.6

A practical chart workflow:

  • Find an existing chart in a repository such as Artifact Hub, or create a starting chart with `helm create hello-joker`. Inspect Chart.yaml, templates/, and values.yaml before changing deployment settings. section 3.3.6
  • Set application-specific values, such as `replicaCount: 3`, an image repository and tag, and a Service type and port. Install the chart into a namespace, then inspect its release with `helm list` and its resources with `kubectl get all`. section 3.3.6
  • For automated releases, have GitLab CI test the application, build and push its Docker image, and update the chart with the new image tag. Point Argo CD at the chart’s path in Git to deploy it and compare live resources with the intended configuration. section 3.4.1 section 3.4.2

A Service change that bypasses Git

Suppose a deployed Service is edited directly from ClusterIP to LoadBalancer. Argo CD marks the application out of sync and shows the difference between the live and expected manifests. When automatic synchronization is enabled, Git remains the source of truth rather than the manual cluster edit. section 3.4.2

How Machine Learning Platform Engineering covers it

How deep it goes
Defines templates and values, then walks through chart creation, installation, inspection, and CI/CD integration without detailing template syntax.
Examples
Uses a Redis chart, a three-replica application chart, and a Service-type edit detected by Argo CD.
What it assumes
Introduces Helm installation and chart commands while requiring a Kubernetes environment and, for the CI example, a configured Docker runtime and Docker Hub.
What you can do after
Operate/configure it by setting chart values, installing and inspecting releases, and connecting chart updates to GitLab CI and Argo CD.
How it connects
Connects Kubernetes manifests, Docker image tags, GitLab CI, and Argo CD through a Git-backed deployment workflow.

Also explained in

Compare how 3 books explain Helm chart →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Machine Learning Platform Engineering. The section links point to the parts of the book it draws on.