You can delete a release by clicking on the 'Delete' button on the desired chart row.

For deletion options, see the[helm delete documentation](https://github.com/kubernetes/helm/blob/master/docs/helm/helm_delete.md), for example,*purge* will remove the revision from the release history.

By default Codefresh will just execute the native Helm command for each GUI action that you press

url="/images/kubernetes-helm/dashboard/override-helm-actions.png"

alt="Changing default Helm actions"

caption="Changing default Helm actions"

max-width="40%"

max-width="50%"

%}

This way you can add your extra logic on top of these actions. For example your own Helm uninstall pipeline might also have a notification step that posts a message to a slack channel after the release is removed.

If you do override any of these actions the following[environment variables]({{site.baseurl}}/docs/codefresh-yaml/variables/) are available in the respective pipeline, so that you can use your own custom helm command.

*Helm Test pipeline*

*`CF_HELM_RELEASE` - name of release

*`CF_HELM_KUBE_CONTEXT` - kubectl context name of target cluster (cluster name from[dashboard]({{site.baseurl}}/docs/deploy-to-kubernetes/manage-kubernetes/#work-with-your-services))

*`CF_HELM_NAMESPACE` - namespace for Tiller Namespace (helm2) or namespace where release is stored (helm3)

*`CF_HELM_TIMEOUT` - time in seconds to wait for any individual Kubernetes operation

*`CF_HELM_CLEANUP` - delete test pods upon completion

*`CF_HELM_TILLER_VERSION` - version of tiller for helm2

*Helm Rollback pipeline*

*`CF_HELM_VERSION` - Helm version, ex.: 3.0.1, 2.7.0

*`CF_HELM_RELEASE` - name of release on cluster

*`CF_HELM_REVISION` - revision which will be used for rollback

*`CF_HELM_KUBE_CONTEXT` - kubectl context name of target cluster (cluster name from[dashboard]({{site.baseurl}}/docs/deploy-to-kubernetes/manage-kubernetes/#work-with-your-services))

*`CF_HELM_NAMESPACE` - namespace for Tiller Namespace (helm2) or namespace where release is stored (helm3)

*Helm delete pipeline*

*`CF_HELM_PURGE` - boolean, delete release from store

*`CF_HELM_RELEASE` - name of release

*`CF_HELM_TIMEOUT` - time in seconds to wait for any individual Kubernetes operation

*`CF_HELM_HOOKS` - prevent hooks from running during install

*`CF_HELM_KUBE_CONTEXT` - kubectl context name of target cluster (cluster name from[dashboard]({{site.baseurl}}/docs/deploy-to-kubernetes/manage-kubernetes/#work-with-your-services))

*`CF_HELM_VERSION` - Helm version, ex.: 3.0.1, 2.7.0

*`CF_HELM_NAMESPACE` - namespace for Tiller Namespace (helm2) or namespace where release is stored (helm3)

- Environment board now supports Helm 3 -[documentation]({{site.baseurl}}/docs/deploy-to-kubernetes/environment-dashboard/)

- Promotion board now supports Helm 3 -[documentation]({{site.baseurl}}/docs/new-helm/helm-environment-promotion/)

- New pipeline Helm step -[documentation]({{site.baseurl}}/docs/new-helm/using-helm-in-codefresh-pipeline/#examples)

- Variables available for Helm pipelines -[documentation]({{site.baseurl}}/docs/new-helm/helm-releases-management/#overriding-the-default-helm-actions)

- Both Helm 2 and Helm 3 clusters can be used at the same time

- Installing the Codefresh runner behind proxy -[documentation]({{site.baseurl}}/docs/enterprise/codefresh-runner/#installing-behind-a-proxy)

- Debugging pipelines with breakpoints -[documentation]({{site.baseurl}}/docs/configure-ci-cd-pipeline/debugging-pipelines/)

- Matrix builds and implicitparalllel steps -[documentation]({{site.baseurl}}/docs/codefresh-yaml/advanced-workflows/#implicit-parallel-steps)

- Matrix builds and implicitparallel steps -[documentation]({{site.baseurl}}/docs/codefresh-yaml/advanced-workflows/#implicit-parallel-steps)

- New Build view filters -[documentation]({{site.baseurl}}/docs/configure-ci-cd-pipeline/monitoring-pipelines/#creating-build-views)

- Deployments with Packer -[documentation]({{site.baseurl}}/docs/yaml-examples/examples/packer-gcloud/)

- Calling child pipelines -[documentation]({{site.baseurl}}/docs/yaml-examples/examples/call-child-pipelines/)

- Approval steps have now timeouts -[documentation]({{site.baseurl}}/docs/codefresh-yaml/steps/approval/#automatic-approvalsrejections)

- Approval steps have now access control -[documentation]({{site.baseurl}}/docs/codefresh-yaml/steps/approval/#approval-restrictions)

- Concurrency limits on pipelines -[documentation]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#pipeline-settings)

- Terminationsetttings on pipelines -[documentation]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#pipeline-settings)

- Terminationsettings on pipelines -[documentation]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#pipeline-settings)

- API keys have now different access scopes -[documentation]({{site.baseurl}}/docs/integrations/codefresh-api/#access-scopes)

- can visually see differences between releases

- Misc:

- UI and bug fixes.

- reorganized Helm docs, including samples on how package charts and push to registry:[Create Helm artifacts using Codefresh pipeline]({{site.baseurl}}/docs/new-helm/create-helm-artifacts-using-codefresh-pipeline/)

- reorganized Helm docs, including samples on how package charts and push to registry:[Create Helm artifacts using Codefresh pipeline]({{site.baseurl}}/docs/new-helm/create-helm-artifacts-using-codefresh-pipeline/)

- Pre-release of our brand new CLI at[https://github.com/codefresh-io/cli](https://github.com/codefresh-io/cli)

- Using our new cli, you can now execute many pipelines in parallel with different configurations for each.

- Easily manage your cluster configuration using Codefresh by creating, importing and sharing Config maps between your Kubernetes namespaces and clusters.

- If you want to trigger Codefresh pipelines from other tool, use our pipeline hook to build, test and deploy from any command line / script / 3rd party.

- Test your cluster Credentials and connectivity in one click.

- We added integration with main self-hosted GIT providers to our PRO plan. You can now use Codefresh with yourrepos from:

- We added integration with main self-hosted GIT providers to our PRO plan. You can now use Codefresh with yourrepositories from:

- GitHub enterprise

- Bitbucket Enterprise

- Gitlab enterprise