Installing a Chart: Basic Deployment
What you'll learn: How to deploy your first application using helm install and understand what a Helm "release" represents.
Understanding Helm Install
Think of a Helm chart as a recipe and helm install as the command that actually cooks the meal. When you install a chart, Helm reads all the templates and values, renders them into Kubernetes manifests, and deploys them to your cluster. This deployed instance is called a release.
The Release Concept
A release is a running instance of a chart in your cluster. You can install the same chart multiple times, and each installation creates a unique release with its own name. This is like deploying the same application blueprint to different environments (dev, staging, production) or running multiple copies with different configurations.
Basic Installation Syntax
The fundamental command structure is:
helm install [RELEASE-NAME] [CHART-NAME]
For example, using a chart from a repository you've added:
helm install my-webapp stable/nginx
This deploys the nginx chart and names the release "my-webapp". Helm automatically generates resource names using the release name as a prefix, keeping everything organized.
You can also let Helm generate a release name:
helm install --generate-name stable/nginx
What Happens During Install
When you run helm install, Helm:
- Downloads the chart (if needed)
- Renders all templates with default or provided values
- Creates all Kubernetes resources in the correct order
- Stores release metadata in a Secret (default) for tracking
Key Takeaway: helm install deploys a chart as a named release—a tracked instance you can upgrade, rollback, or uninstall independently, making application lifecycle management repeatable and versioned.