Helm 安装

    该命令用于安装chart包。

    安装参数必须是chart的引用，一个打包后的chart路径，未打包的chart目录或者是一个URL。

    要重写chart中的值，使用’—values’参数传递一个文件或者使用’—set’参数在命令行传递配置，强制使用字符串要用’—set-string’。 当值本身对于命令行太长或者是动态生成的时候，可以使用 ‘—set-file’ 设置独立的值。

    或者

    1. $ helm install --set-string long_int=1234567890 myredis ./redis

    或者

    你可以多次指定’—values’/‘-f’参数。最右侧指定的文件优先级最高。比如，如果两个文件myvalues.yaml和override.yaml 都包含名为’Test’的可以，override.yaml中的值优先：

    1. $ helm install -f myvalues.yaml -f override.yaml  myredis ./redis

    可以指定’—set’参数多次，最右边的参数优先级最高，比如，’bar’和’newbar’都设置了一个名为’foo’的可以，’newbar’的值优先：

    1.     $ helm install --set foo=bar --set foo=newbar  myredis ./redis

    为了检测生成的清单，但并不安装到chart，可以将’—debug’和’—dry-run’组合使用。

    有五种不同的方式来标识需要安装的chart：

    1. 通过chart引用： helm install mymaria example/mariadb
    2. 通过chart包： helm install mynginx ./nginx-1.2.3.tgz
    3. 通过未打包chart目录的路径： helm install mynginx ./nginx
    4. 通过URL绝对路径： helm install mynginx https://example.com/charts/nginx-1.2.3.tgz
    5. 通过chart引用和仓库url： helm install —repo mynginx nginx

    CHART引用

    chart引用是在chart仓库中引用chart的一种方便方式。

    当你用仓库前缀(‘example/mariadb’)引用chart时，Helm会在本地配置查找名为 ‘example’ 的chart仓库， 然后会在仓库中查找名为’mariadb’的仓库，然后会安装这个chart最新的稳定版本，除非指定了’—devel’参数且包含了开发版本(alpha， beta，和候选版本)，或者使用’—version’参数提供一个版本号。

    1.       --atomic                       if set, the installation process deletes the installation on failure. The --wait flag will be set automatically if --atomic is used
    2.       --ca-file string               verify certificates of HTTPS-enabled servers using this CA bundle
    3.       --cert-file string             identify HTTPS client using this SSL certificate file
    4.       --create-namespace             create the release namespace if not present
    5.       --dependency-update            update dependencies if they are missing before installing the chart
    6.       --devel                        use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored
    7.       --disable-openapi-validation   if set, the installation process will not validate rendered templates against the Kubernetes OpenAPI Schema
    8.       --dry-run                      simulate an install
    9.   -g, --generate-name                generate the name (and omit the NAME parameter)
    10.   -h, --help                         help for install
    11.       --insecure-skip-tls-verify     skip tls certificate checks for the chart download
    13.       --keyring string               location of public keys used for verification (default "~/.gnupg/pubring.gpg")
    14.       --name-template string         specify template used to name the release
    15.       --no-hooks                     prevent hooks from running during install
    16.   -o, --output format                prints the output in the specified format. Allowed values: table, json, yaml (default table)
    17.       --pass-credentials             pass credentials to all domains
    18.       --password string              chart repository password where to locate the requested chart
    19.       --post-renderer postrenderer   the path to an executable to be used for post rendering. If it exists in $PATH, the binary will be used, otherwise it will try to look for the executable at the given path (default exec)
    20.       --render-subchart-notes        if set, render subchart notes along with the parent
    21.       --replace                      re-use the given name, only if that name is a deleted release which remains in the history. This is unsafe in production
    22.       --repo string                  chart repository url where to locate the requested chart
    23.       --set stringArray              set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
    24.       --set-file stringArray         set values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
    25.       --skip-crds                    if set, no CRDs will be installed. By default, CRDs are installed if not already present
    26.       --timeout duration             time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)
    28.   -f, --values strings               specify values in a YAML file or a URL (can specify multiple)
    29.       --verify                       verify the package before using it
    30.       --version string               specify a version constraint for the chart version to use. This constraint can be a specific tag (e.g. 1.1.1) or it may reference a valid range (e.g. ^2.0.0). If this is not specified, the latest version is used
    31.       --wait                         if set, will wait until all Pods, PVCs, Services, and minimum number of Pods of a Deployment, StatefulSet, or ReplicaSet are in a ready state before marking the release as successful. It will wait for as long as --timeout
    1.       --debug                       enable verbose output
    2.       --kube-apiserver string       the address and the port for the Kubernetes API server
    3.       --kube-as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups.
    4.       --kube-as-user string         username to impersonate for the operation
    5.       --kube-context string         name of the kubeconfig context to use
    6.       --kube-token string           bearer token used for authentication
    7.       --kubeconfig string           path to the kubeconfig file
    8.   -n, --namespace string            namespace scope for this request
    9.       --registry-config string      path to the registry config file (default "~/.config/helm/registry/config.json")
    10.       --repository-cache string     path to the file containing cached repository indexes (default "~/.cache/helm/repository")
    11.       --repository-config string    path to the file containing repository names and URLs (default "~/.config/helm/repositories.yaml")
    • helm - 针对Kubernetes的Helm包管理器