Public Chart Rendering

What problem this solves

Public charts are useful integration checks because they exercise helpers, nested values, capabilities, CRDs, and formatting patterns that small sample charts often miss. Use this workflow when you want to preview a pinned public chart and inspect the generated manifests before a release.

Packages to install

dotnet add package HelmSharp.Action --version 1.1.0

Minimal complete code

var result = await client.TemplateAsync(new HelmTemplateRequest
{
    ReleaseName = "ingress-nginx",
    Namespace = "ingress-system",
    Chart = "/charts/ingress-nginx",
    ValuesFiles = ["ci/controller-deployment-values.yaml"],
    KubeVersion = "1.30.0",
    ApiVersions =
    [
        "networking.k8s.io/v1",
        "policy/v1",
        "monitoring.coreos.com/v1"
    ],
    IncludeCRDs = true,
    ShowNotes = true
}, cancellationToken);

Console.WriteLine(result.StandardOutput);

Why these APIs

HelmTemplateRequest maps to the preview shape many Helm users already know: release, namespace, chart, values, kube version, API versions, CRDs, and notes.

Production notes

• Pin chart versions when rendering public charts.
• Keep the chart copy or chart provenance tied to the preview output.
• Use the compatibility page for current public-chart test coverage and known boundaries.

Next step

Open Helm Compatibility for the full 1.1.0 matrix.