Difference between revisions of "Helm dependency"

From NovaOrdis Knowledge Base
Jump to: navigation, search
(Dependency Update)
(Overview)
Line 9: Line 9:
  
 
=Overview=
 
=Overview=
 +
 +
The helm dependency command operates on requirements.yaml file, with the aim of maintaining the content of the charts/ subdirectory in sync with requirements.yaml. For an in-depth discussion on how Helm dependencies work, see: {{Internal|Helm_Dependencies#How_Helm_Dependencies_Work|How Helm Dependencies Work}}
  
 
=Dependency Update=
 
=Dependency Update=

Revision as of 00:14, 14 September 2019

External

Internal

Overview

The helm dependency command operates on requirements.yaml file, with the aim of maintaining the content of the charts/ subdirectory in sync with requirements.yaml. For an in-depth discussion on how Helm dependencies work, see:
How Helm Dependencies Work

Dependency Update

helm dependency update
helm dep up

When this command retrieves charts, it will store them as chart archives in the charts/ directory of the dependent chart:

helm dependency update postgresql-dynamic-dependency/
Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):
	Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused
...Successfully got an update from the "incubator" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
Saving 1 charts
Downloading postgresql from repo https://kubernetes-charts.storage.googleapis.com
Deleting outdated charts

As result, postgresql-6.3.2.tgz is placed into the dependent chart's charts/ directory.

The command recreates requirements.lock.