> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/helm/step-reference/helm-canary-deploy.md).

# Helm Canary Deploy Step

Reference for the Helm Canary Deploy step

This topic describes the configuration and settings for the Helm Canary Deploy step.

The Helm Canary Deploy step deploys using a canary based strategy. To learn more, go to [Harness canary deployments](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/kubernetes-executions/create-a-kubernetes-canary-deployment.md#harness-canary-deployments).

You may want to delete resources created by this step. To do so, use the [Helm Canary Delete](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/helm/step-reference/helm-canary-delete.md) step.

{% hint style="info" %}
Harness Delegate version 84300 or later is required for this feature.
{% endhint %}

### Name <a href="#name" id="name"></a>

The name for the deploy step.

### Timeout <a href="#timeout" id="timeout"></a>

Enter a timeout for this step. You can use:

* `w` for weeks
* `d` for days
* `h` for hours
* `m` for minutes
* `s` for seconds
* `ms` for milliseconds

### Instances <a href="#instances" id="instances"></a>

In Instances, select **Instance Count** or **Percentage**.

In Instances, enter the number of pods to deploy.

If you selected Instance Count, enter the number of pods.

If you selected Percentage, enter a percentage of the pods defined in your Service Definition Manifests files to deploy.

For example, in you have replicas: 4 in a manifest in Service, and you enter 50 in Instances, then 2 pods are deployed in this Phase step.

### Ignore Release History Failed Status <a href="#ignore-release-history-failed-status" id="ignore-release-history-failed-status"></a>

By default, if the latest Helm release failed, Harness does not proceed with the install/upgrade and throws an error.

Enable this option to have Harness ignore these errors and proceed with install/upgrade.

### Skip Steady State Check <a href="#skip-steady-state-check" id="skip-steady-state-check"></a>

By default, Harness checks to see if a deployed workload has reached steady state.

If you select this option, Harness will not check that the workload has reached steady state.

### Optional Configuration <a href="#optional-configuration" id="optional-configuration"></a>

Add any environment variables here.

### Advanced Options <a href="#advanced-options" id="advanced-options"></a>

See the following:

* [Delegate Selector](/harness-ai/use-harness-platform/delegates/delegate/manage-delegates/select-delegates-with-selectors.md)
* [Conditional Execution](/harness-ai/use-harness-platform/pipelines/step-skip-condition-settings.md)
* [Failure Strategy](/harness-ai/use-harness-platform/pipelines/failure-handling/define-a-failure-strategy-on-stages-and-steps.md)
* [Looping Strategy](/harness-ai/use-harness-platform/pipelines/looping-strategies/looping-strategies-matrix-repeat-and-parallelism.md)
* [Policy Enforcement](/harness-ai/use-harness-platform/governance/policy-as-code/harness-governance-overview.md)
* [Command Flags](/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/helm/native-helm-quickstart.md#configure-command-flags-at-step-level)

{% @harness-feedback/feedback %}