Updated Oct 16, 2026

Utilities

Render a self-contained Helm chart offline

helm-render is an offline rendering node for self-contained Helm charts.

Agent

overview

What helm-render does

Supply a folder with Chart.yaml at its root, templates and optional values.yaml. Helm template renders Kubernetes YAML, including CRDs, with the release name fixture, namespace default and Kubernetes 1.34.0 capabilities. Dependencies are not installed.

Use trusted templates only. Charts must be self-contained; dependency charts and symbolic links are refused. The limits are 500 files, 10 MiB input, 60 seconds and 16 MiB output. User Helm plugins/configuration are isolated.

Input or native processing failures fail the operation. The operation keeps the supplied source unchanged.

This operation uses 4.3.1. Upstream license: Apache-2.0. The source link identifies the program used by this node.

source github.com/helm/helm/tree/v4.3.1

use cases

Where helm-render fits

Inspect template expansion

Expand a self-contained chart using fixed release and capability values.

Review rendered values

Check how values.yaml appears in the resulting Kubernetes manifests.

Produce manifests without a cluster

Produce YAML without credentials or any cluster request.

reference

helm-render inputs and flags

1 inputs
NameTypeFlagDescription
chartFOLDER--chartChart.yaml at folder root, templates and optional values.yaml. No dependency charts or symlinks; 500 files/10 MiB, 60 seconds, 16 MiB output. Fixed fixture release, default namespace and Kubernetes 1.34.0 capabilities. Trusted templates only.

Showing key inputs. helm-render exposes 1 inputs in total.

example

Run helm-render

helm-render · command
python3 /app/run.py --chart ./source ./output
sample output
{
  "kind": "ConfigMap",
  "metadata": {
    "name": "fixture-config",
    "namespace": "default"
  },
  "data": {
    "greeting": "Café fixture",
    "replicas": "3",
    "kubernetes": "v1.34.0"
  }
}

guidance

Choosing helm-render

Use this node to inspect template expansion for a self-contained chart. Rendering does not show whether a live cluster accepts the resources, and no installation or deployment occurs.

yq

Queries YAML documents; Helm expands chart templates into manifests.

faq

helm-render questions

chart: Chart.yaml at folder root, templates and optional values.yaml. No dependency charts or symlinks; 500 files/10 MiB, 60 seconds, 16 MiB output. Fixed fixture release, default namespace and Kubernetes 1.34.0 capabilities. Trusted templates only.

Kubernetes YAML. Native processing must succeed before an output artifact is returned.

Use trusted templates only. Charts must be self-contained; dependency charts and symbolic links are refused. The limits are 500 files, 10 MiB input, 60 seconds and 16 MiB output. User Helm plugins/configuration are isolated.

Use this node to inspect template expansion for a self-contained chart. Rendering does not show whether a live cluster accepts the resources, and no installation or deployment occurs.

The image repository also contains a digest-bound source/notices artifact. Download it with oras pull docker.io/nenadzaric/skills-intel-helm-render@sha256:4a734453de8a18901fdf5670eb8cc853acb31f3086e139f17ebc09a36098ea88. The bundle includes the build recipe, licenses, copied notices and component-source directions. Bundle SHA256: 69466fada6f64509f54f8d0e25558909cc44cbf24d064724bb5c4a3aeddbe32c. Follow its source directions for upstream archives and patches. Image and source/notices repository.

Run helm-render yourself

The synthetic run checks kubernetes yaml. The excerpt shows selected native fields asserted by saved passing platform verifier; reconstructed excerpt, not full raw artifact. The command shown is the container entrypoint with example paths, not a host-installed CLI command.

Facts on this page come from the live Trickest tool library.