From 57daa56b8156d35f9b6b0fc31baec429fab1b3ba Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christoph=20H=C3=B6sler?= Date: Wed, 22 Nov 2017 13:17:18 +0100 Subject: [PATCH] Update installDesc --- cmd/helm/install.go | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/cmd/helm/install.go b/cmd/helm/install.go index df9bf09fb..bc44bd0e4 100644 --- a/cmd/helm/install.go +++ b/cmd/helm/install.go @@ -79,18 +79,19 @@ round-trip to the Tiller server. If --verify is set, the chart MUST have a provenance file, and the provenenace fall MUST pass all verification steps. -There are four different ways you can express the chart you want to install: +There are five different ways you can express the chart you want to install: 1. By chart reference: helm install stable/mariadb 2. By path to a packaged chart: helm install ./nginx-1.2.3.tgz 3. By path to an unpacked chart directory: helm install ./nginx 4. By absolute URL: helm install https://example.com/charts/nginx-1.2.3.tgz +5. By chart reference and repo url: helm install --repo https://example.com/charts nginx CHART REFERENCES A chart reference is a convenient way of reference a chart in a chart repository. -When you use a chart reference ('stable/mariadb'), Helm will look in the local +When you use a chart reference with a repo prefix ('stable/mariadb'), Helm will look in the local configuration for a chart repository named 'stable', and will then look for a chart in that repository whose name is 'mariadb'. It will install the latest version of that chart unless you also supply a version number with the