Helm Dependencies: Difference between revisions
Jump to navigation
Jump to search
| Line 48: | Line 48: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
=Packaging and Dependencies= | =Packaging and Dependencies= | ||
{{Internal| | {{Internal|Helm_package#Packaging_and_Dependencies|Packaging and Dependencies}} | ||
=Dependencies and Values= | =Dependencies and Values= | ||
=Dependency Operations= | =Dependency Operations= | ||
Revision as of 21:25, 15 December 2019
External
Internal
Overview
Revised for Helm 3
To Deplete
How Helm Dependencies Work
Helm does not automatically handle transitive dependencies, in the manner that Maven, for example, does. Intermediate manual steps are required to install a chart that depends on other charts.
If we simply declare the chart "a" as dependent on chart "b" in the dependencies section of the "a"'s Chart and we attempt to install the chart "a", we get this:
Error: found in Chart.yaml, but missing in charts/ directory: b
What happens if a-1.0.0.zip is in a remote repository and does not have its dependencies in charts/?
Dependency Declaration
Dependencies are declared in Chart.yaml 'dependencies' section.
...
dependencies:
- name: # The name of the dependency
version: # The version of the dependency
repository: # Repository URL
...
Example:
...
# 'a' Chart.yaml
dependencies:
- name: b
version: 1.0.0
repository: # Repository URL
...