Helm Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 54: | Line 54: | ||
The server is responsible for managing [[#Release|releases]]. | The server is responsible for managing [[#Release|releases]]. | ||
Tiller stores release information in [[Kubernetes_Cluster_Configuration_Concepts#ConfigMap|ConfigMaps]] in the namespace where it is running. | |||
=Security= | =Security= | ||
{{Internal|Helm Security Concepts|Security Concepts}} | {{Internal|Helm Security Concepts|Security Concepts}} | ||
Revision as of 16:18, 28 August 2019
Internal
Overview
Chart
Chart Archive
Chart Operations
Config
Template
Release
A release is a running instantiation of a chart, to which a specific config was applied. Whenever a chart is installed, a new release is created. One chart can be installed multiple times into the same cluster, and each can be independently managed and upgraded.
Release Operations
Repository
Repository Operations
Dependency
- If I rely on a dependency referred from an external Helm repository, and the repository exposes newer versions, can I still rely on the fact that the old version is still available? I might not want to upgrade to the "latest", but keep using a version I tested with and was proven stable.
Runtime
The Helm Client
The client is responsible for managing charts.
The Tiller Server
The server is responsible for managing releases.
Tiller stores release information in ConfigMaps in the namespace where it is running.