> 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-deploy.md).

# Helm Deploy Step

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

The Helm Deploy step performs a rolling deployment strategy.

### 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

### 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.

### Use Upgrade with Install <a href="#use-upgrade-with-install" id="use-upgrade-with-install"></a>

Select this option to use "helm upgrade --install" instead of "helm install", allowing upgrades if the release already exists.

### Skip Cleanup <a href="#skip-cleanup" id="skip-cleanup"></a>

**Default:** `false` This setting prevents the automatic uninstallation of failed Helm releases. When set to `true`, failed releases remain in the cluster for debugging. Manual cleanup is required when using this setting.

### 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)