github.com/koderover/helm@v2.17.0+incompatible/docs/man/man1/helm_install.1 (about)

     1  .TH "HELM" "1" "May 2017" "Auto generated by spf13/cobra" "" 
     2  .nh
     3  .ad l
     4  
     5  
     6  .SH NAME
     7  .PP
     8  helm\-install \- install a chart archive
     9  
    10  
    11  .SH SYNOPSIS
    12  .PP
    13  \fBhelm install [CHART]\fP
    14  
    15  
    16  .SH DESCRIPTION
    17  .PP
    18  This command installs a chart archive.
    19  
    20  .PP
    21  The install argument must be a chart reference, a path to a packaged chart,
    22  a path to an unpacked chart directory or a URL.
    23  
    24  .PP
    25  To override values in a chart, use either the '\-\-values' flag and pass in a file
    26  or use the '\-\-set' flag and pass configuration from the command line.
    27  
    28  .PP
    29  .RS
    30  
    31  .nf
    32  $ helm install \-f myvalues.yaml ./redis
    33  
    34  .fi
    35  .RE
    36  
    37  .PP
    38  or
    39  
    40  .PP
    41  .RS
    42  
    43  .nf
    44  $ helm install \-\-set name=prod ./redis
    45  
    46  .fi
    47  .RE
    48  
    49  .PP
    50  You can specify the '\-\-values'/'\-f' flag multiple times. The priority will be given to the
    51  last (right\-most) file specified. For example, if both myvalues.yaml and override.yaml
    52  contained a key called 'Test', the value set in override.yaml would take precedence:
    53  
    54  .PP
    55  .RS
    56  
    57  .nf
    58  $ helm install \-f myvalues.yaml \-f override.yaml ./redis
    59  
    60  .fi
    61  .RE
    62  
    63  .PP
    64  You can specify the '\-\-set' flag multiple times. The priority will be given to the
    65  last (right\-most) set specified. For example, if both 'bar' and 'newbar' values are
    66  set for a key called 'foo', the 'newbar' value would take precedence:
    67  
    68  .PP
    69  .RS
    70  
    71  .nf
    72  $ helm install \-\-set foo=bar \-\-set foo=newbar ./redis
    73  
    74  .fi
    75  .RE
    76  
    77  .PP
    78  To check the generated manifests of a release without installing the chart,
    79  the '\-\-debug' and '\-\-dry\-run' flags can be combined. This will still require a
    80  round\-trip to the Tiller server.
    81  
    82  .PP
    83  If \-\-verify is set, the chart MUST have a provenance file, and the provenance
    84  fall MUST pass all verification steps.
    85  
    86  .PP
    87  There are four different ways you can express the chart you want to install:
    88  .IP "  1." 5
    89  By chart reference: helm install stable/mariadb
    90  .IP "  2." 5
    91  By path to a packaged chart: helm install ./nginx\-1.2.3.tgz
    92  .IP "  3." 5
    93  By path to an unpacked chart directory: helm install ./nginx
    94  .IP "  4." 5
    95  By absolute URL: helm install 
    96  \[la]https://example.com/charts/nginx-1.2.3.tgz\[ra]
    97  
    98  .PP
    99  CHART REFERENCES
   100  
   101  .PP
   102  A chart reference is a convenient way of reference a chart in a chart repository.
   103  
   104  .PP
   105  When you use a chart reference ('stable/mariadb'), Helm will look in the local
   106  configuration for a chart repository named 'stable', and will then look for a
   107  chart in that repository whose name is 'mariadb'. It will install the latest
   108  version of that chart unless you also supply a version number with the
   109  '\-\-version' flag.
   110  
   111  .PP
   112  To see the list of chart repositories, use 'helm repo list'. To search for
   113  charts in a repository, use 'helm search'.
   114  
   115  
   116  .SH OPTIONS
   117  .PP
   118  \fB\-\-ca\-file\fP=""
   119      verify certificates of HTTPS\-enabled servers using this CA bundle
   120  
   121  .PP
   122  \fB\-\-cert\-file\fP=""
   123      identify HTTPS client using this SSL certificate file
   124  
   125  .PP
   126  \fB\-\-dep\-up\fP[=false]
   127      run helm dependency update before installing the chart.
   128  
   129  .PP
   130  \fB\-\-devel\fP[=false]
   131      use development versions, too. Equivalent to version '>0.0.0\-a'. If \-\-version is set, this is ignored.
   132  
   133  .PP
   134  \fB\-\-dry\-run\fP[=false]
   135      simulate an install
   136  
   137  .PP
   138  \fB\-\-key\-file\fP=""
   139      identify HTTPS client using this SSL key file
   140  
   141  .PP
   142  \fB\-\-keyring\fP="~/.gnupg/pubring.gpg"
   143      location of public keys used for verification
   144  
   145  .PP
   146  \fB\-n\fP, \fB\-\-name\fP=""
   147      release name. If unspecified, it will autogenerate one for you
   148  
   149  .PP
   150  \fB\-\-name\-template\fP=""
   151      specify template used to name the release
   152  
   153  .PP
   154  \fB\-\-namespace\fP=""
   155      namespace to install the release into
   156  
   157  .PP
   158  \fB\-\-no\-hooks\fP[=false]
   159      prevent hooks from running during install
   160  
   161  .PP
   162  \fB\-\-replace\fP[=false]
   163      re\-use the given name, even if that name is already used. This is unsafe in production
   164  
   165  .PP
   166  \fB\-\-repo\fP=""
   167      chart repository url where to locate the requested chart
   168  
   169  .PP
   170  \fB\-\-set\fP=[]
   171      set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
   172  
   173  .PP
   174  \fB\-\-timeout\fP=300
   175      time in seconds to wait for any individual kubernetes operation (like Jobs for hooks)
   176  
   177  .PP
   178  \fB\-\-tls\fP[=false]
   179      enable TLS for request
   180  
   181  .PP
   182  \fB\-\-tls\-ca\-cert\fP="$HELM\_HOME/ca.pem"
   183      path to TLS CA certificate file
   184  
   185  .PP
   186  \fB\-\-tls\-cert\fP="$HELM\_HOME/cert.pem"
   187      path to TLS certificate file
   188  
   189  .PP
   190  \fB\-\-tls\-key\fP="$HELM\_HOME/key.pem"
   191      path to TLS key file
   192  
   193  .PP
   194  \fB\-\-tls\-verify\fP[=false]
   195      enable TLS for request and verify remote
   196  
   197  .PP
   198  \fB\-f\fP, \fB\-\-values\fP=[]
   199      specify values in a YAML file or a URL(can specify multiple)
   200  
   201  .PP
   202  \fB\-\-verify\fP[=false]
   203      verify the package before installing it
   204  
   205  .PP
   206  \fB\-\-version\fP=""
   207      specify the exact chart version to install. If this is not specified, the latest version is installed
   208  
   209  .PP
   210  \fB\-\-wait\fP[=false]
   211      if set, will wait until all Pods, PVCs, Services, and minimum number of Pods of a Deployment are in a ready state before marking the release as successful. It will wait for as long as \-\-timeout
   212  
   213  
   214  .SH OPTIONS INHERITED FROM PARENT COMMANDS
   215  .PP
   216  \fB\-\-debug\fP[=false]
   217      enable verbose output
   218  
   219  .PP
   220  \fB\-\-home\fP="~/.helm"
   221      location of your Helm config. Overrides $HELM\_HOME
   222  
   223  .PP
   224  \fB\-\-host\fP="localhost:44134"
   225      address of tiller. Overrides $HELM\_HOST
   226  
   227  .PP
   228  \fB\-\-kube\-context\fP=""
   229      name of the kubeconfig context to use
   230  
   231  .PP
   232  \fB\-\-tiller\-namespace\fP="kube\-system"
   233      namespace of tiller
   234  
   235  
   236  .SH SEE ALSO
   237  .PP
   238  \fBhelm(1)\fP
   239  
   240  
   241  .SH HISTORY
   242  .PP
   243  31\-Oct\-2017 Auto generated by spf13/cobra