f012940d9c
ref(chartutil): move chart loading out of chartutil into new package
add chart loader interface to allow lazy loading
feat(chart): create chart accessors
ref(*): cleanup requirements
ref(tiller): remove optional template engines
ref(tiller): simplify sorting releases and hooks
ref(*): code simplification
ref(hapi): move chart package out of hapi
ref(chart): add requirements and lock to Chart struct
|
||
|---|---|---|
| .. | ||
| charts/alpine | ||
| templates | ||
| .helmignore | ||
| Chart.yaml | ||
| README.md | ||
| values.yaml | ||
nginx: An advanced example chart
This Helm chart provides examples of some of Helm's more powerful features.
This is not a production-grade chart. It is an example.
The chart installs a simple nginx server according to the following pattern:
- A
ConfigMapis used to store the files the server will serve. (templates/configmap.yaml) - A
Deploymentis used to create a Replica Set of nginx pods. (templates/deployment.yaml) - A
Serviceis used to create a gateway to the pods running in the replica set (templates/service.yaml)
The values.yaml exposes a few of the configuration options in the
charts, though there are some that are not exposed there (like
.image).
The templates/_helpers.tpl file contains helper templates. The leading
underscore (_) on the filename is semantic. It tells the template renderer
that this file does not contain a manifest. That file declares some
templates that are used elsewhere in the chart.
Helpers (usually called "partials" in template languages) are an advanced way for developers to structure their templates for optimal reuse.
You can deploy this chart with helm install docs/examples/nginx. Or
you can see how this chart would render with helm install --dry-run --debug docs/examples/nginx.