helm template
Locally render templates
Options
| Name | Description | 
|---|---|
| --api-versions, -a  <api-versions> | 
 | 
| --atomic | If set, the installation process deletes the installation on failure. The --wait flag will be set automatically if --atomic is used | 
| --ca-file  <ca-file> | Verify certificates of HTTPS-enabled servers using this CA bundle | 
| --cert-file  <cert-file> | 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  <description> | 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 | 
| --generate-name, -g | Generate the name (and omit the NAME parameter) | 
| --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  <key-file> | Identify HTTPS client using this SSL key file | 
| --keyring  <keyring> | Location of public keys used for verification | 
| --kube-version  <kube-version> | Kubernetes version used for Capabilities.KubeVersion | 
| --name-template  <name-template> | Specify template used to name the release | 
| --no-hooks | Prevent hooks from running during install | 
| --output-dir  <output-dir> | Writes the executed templates to files in output-dir instead of stdout | 
| --pass-credentials | Pass credentials to all domains | 
| --password  <password> | Chart repository password where to locate the requested chart | 
| --post-renderer  <post-renderer> | 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  <post-renderer-args> | 
 | 
| --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  <repo> | Chart repository url where to locate the requested chart | 
| --set  <set> | 
 | 
| --set-file  <set-file> | 
 | 
| --set-string  <set-string> | 
 | 
| --show-only, -s  <show-only> | 
 | 
| --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  <timeout> | Time to wait for any individual Kubernetes operation (like Jobs for hooks) | 
| --username  <username> | 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 | 
| --values, -f  <values> | 
 | 
| --verify | Verify the package before using it | 
| --version  <version> | 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 |