github.com/koderover/helm@v2.17.0+incompatible/docs/chart_template_guide/debugging.md (about)

     1  # Debugging Templates
     2  
     3  Debugging templates can be tricky simply because the templates are rendered on the Tiller server, not the Helm client. And then the rendered templates are sent to the Kubernetes API server, which may reject the YAML files for reasons other than formatting.
     4  
     5  There are a few commands that can help you debug.
     6  
     7  - `helm lint` is your go-to tool for verifying that your chart follows best practices
     8  - `helm install --dry-run --debug`: We've seen this trick already. It's a great way to have the server render your templates, then return the resulting manifest file.
     9  - `helm get manifest`: This is a good way to see what templates are installed on the server.
    10  
    11  When your YAML is failing to parse, but you want to see what is generated, one
    12  easy way to retrieve the YAML is to comment out the problem section in the template,
    13  and then re-run `helm install --dry-run --debug`:
    14  
    15  ```yaml
    16  apiVersion: v1
    17  # some: problem section
    18  # {{ .Values.foo | quote }}
    19  ```
    20  
    21  The above will be rendered and returned with the comments intact:
    22  
    23  ```yaml
    24  apiVersion: v1
    25  # some: problem section
    26  #  "bar"
    27  ```
    28  
    29  This provides a quick way of viewing the generated content without YAML parse
    30  errors blocking.