mirror of https://github.com/helm/helm
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Adam Reese
dee2a1a000
|
6 years ago | |
|---|---|---|
| .. | ||
| README.md | 6 years ago | |
| conventions.md | 6 years ago | |
| custom_resource_definitions.md | ||
| labels.md | 6 years ago | |
| pods.md | ||
| rbac.md | ||
| requirements.md | 6 years ago | |
| templates.md | ||
| values.md | ||
README.md
The Chart Best Practices Guide
This guide covers the Helm Team's considered best practices for creating charts. It focuses on how charts should be structured.
We focus primarily on best practices for charts that may be publicly deployed. We know that many charts are for internal-use only, and authors of such charts may find that their internal interests override our suggestions here.
Table of Contents
- General Conventions: Learn about general chart conventions.
- Values Files: See the best practices for structuring
values.yaml. - Templates: Learn some of the best techniques for writing templates.
- Dependencies: Follow best practices for
dependenciesdeclared inChart.yaml. - Labels and Annotations: Helm has a heritage of labeling and annotating.
- Kubernetes Resources:
- Pods and Pod Specs: See the best practices for working with pod specifications.
- Role-Based Access Control: Guidance on creating and using service accounts, roles, and role bindings.
- Third Party Resources: Third Party Resources (TPRs) have their own associated best practices.