我的书签
添加书签
移除书签Helm Template
helm template
locally render templates
Synopsis
Render chart templates locally and display the output.
Any values that would normally be looked up or retrieved in-cluster will be faked locally. Additionally, none of the server-side testing of chart validity (e.g. whether an API is supported) is done.
helm template [NAME] [CHART] [flags]
Options
-a, --api-versions stringArray Kubernetes api versions used for Capabilities.APIVersions--atomic if set, the installation process deletes the installation on failure. The --wait flag will be set automatically if --atomic is used--ca-file string verify certificates of HTTPS-enabled servers using this CA bundle--cert-file string identify HTTPS client using this SSL certificate file--create-namespace create the release namespace if not present--dependency-update update dependencies if they are missing before installing the chart--description string add a custom description--devel use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored--disable-openapi-validation if set, the installation process will not validate rendered templates against the Kubernetes OpenAPI Schema--dry-run simulate an install-g, --generate-name generate the name (and omit the NAME parameter)-h, --help help for template--include-crds include CRDs in the templated output--insecure-skip-tls-verify skip tls certificate checks for the chart download--is-upgrade set .Release.IsUpgrade instead of .Release.IsInstall--key-file string identify HTTPS client using this SSL key file--keyring string location of public keys used for verification (default "~/.gnupg/pubring.gpg")--kube-version string Kubernetes version used for Capabilities.KubeVersion--name-template string specify template used to name the release--no-hooks prevent hooks from running during install--output-dir string writes the executed templates to files in output-dir instead of stdout--pass-credentials pass credentials to all domains--password string chart repository password where to locate the requested chart--post-renderer postRendererString 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--post-renderer-args postRendererArgsSlice an argument to the post-renderer (can specify multiple) (default [])--release-name use release name in the output-dir path.--render-subchart-notes if set, render subchart notes along with the parent--replace re-use the given name, only if that name is a deleted release which remains in the history. This is unsafe in production--repo string chart repository url where to locate the requested chart--set stringArray set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)--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)--set-string stringArray set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)-s, --show-only stringArray only show manifests rendered from the given templates--skip-crds if set, no CRDs will be installed. By default, CRDs are installed if not already present--skip-tests skip tests from templated output--timeout duration time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)--username string chart repository username where to locate the requested chart--validate validate your manifests against the Kubernetes cluster you are currently pointing at. This is the same validation performed on an install-f, --values strings specify values in a YAML file or a URL (can specify multiple)--verify verify the package before using it--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--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--wait-for-jobs if set and --wait enabled, will wait until all Jobs have been completed before marking the release as successful. It will wait for as long as --timeout
Options inherited from parent commands
--debug enable verbose output--kube-apiserver string the address and the port for the Kubernetes API server--kube-as-group stringArray group to impersonate for the operation, this flag can be repeated to specify multiple groups.--kube-as-user string username to impersonate for the operation--kube-ca-file string the certificate authority file for the Kubernetes API server connection--kube-context string name of the kubeconfig context to use--kube-token string bearer token used for authentication--kubeconfig string path to the kubeconfig file-n, --namespace string namespace scope for this request--registry-config string path to the registry config file (default "~/.config/helm/registry/config.json")--repository-cache string path to the file containing cached repository indexes (default "~/.cache/helm/repository")--repository-config string path to the file containing repository names and URLs (default "~/.config/helm/repositories.yaml")
SEE ALSO
- helm - The Helm package manager for Kubernetes.
