Release Workflows

What problem this solves

Release workflows combine rendering, Kubernetes apply/delete/wait, hooks, and release history. Use this path when your application owns a deployment action, not just a preview.

Packages to install

dotnet add package HelmSharp.Action --version 1.1.0

Minimal complete code

Start with a dry run:

public static async Task<CommandResult> DryRunReleaseAsync(
    string chartPath,
    IHelmOptionsProvider optionsProvider,
    CancellationToken cancellationToken)
{
    var client = new HelmClient(optionsProvider);

    return await client.UpgradeInstallAsync(new HelmUpgradeInstallRequest
    {
        ReleaseName = "demo",
        Namespace = "default",
        Chart = chartPath,
        ValuesFiles = ["values.production.yaml"],
        CreateNamespace = true,
        Wait = true,
        TimeoutSeconds = 300,
        DryRun = true
    }, cancellationToken);
}

Apply only after approval:

public static async Task<CommandResult> ApplyReleaseAfterApprovalAsync(
    string chartPath,
    IHelmOptionsProvider optionsProvider,
    CancellationToken cancellationToken)
{
    var client = new HelmClient(optionsProvider);

    return await client.UpgradeInstallAsync(new HelmUpgradeInstallRequest
    {
        ReleaseName = "demo",
        Namespace = "default",
        Chart = chartPath,
        ValuesFiles = ["values.production.yaml"],
        CreateNamespace = true,
        Wait = true,
        WaitForJobs = true,
        TimeoutSeconds = 300,
        DryRun = false
    }, cancellationToken);
}

Why these APIs

HelmClient.UpgradeInstallAsync is the primary install/upgrade entry point. It loads the chart, merges values, renders manifests, applies CRDs when needed, executes hooks unless disabled, waits for readiness when requested, and saves release history.

Production notes

• Keep DryRun = true in preview flows and switch to false only in the approved apply step.
• Set TimeoutSeconds, Wait, and WaitForJobs explicitly so UI and API timeouts match deployment semantics.
• Capture CommandResult.StandardError and ExitCode in product logs.

Next step

Read Kubernetes Operations for lower-level apply/delete/wait behavior.