# Helm based deployment to Kubernetes namespace

Helm Chart is a packaging tool for Kubernetes. It packages all of your disparate manifests as a singular object to advertise to your cluster.

 To deploy a helm chart, follow the steps below:

1. **Go to** [**Application Dashboard**](https://docs.opsmx.com/user-guide/dashboard/application-dashboard): When you log in to ISD the application dashboard is displayed with the list of applications. You can create a new application also as given in [**create a new application**](https://docs.opsmx.com/release-history/previous-releases/isd-4.0/knowledge-base/manage-application/create-an-application). 
2. Click on the application for which you want to build this pipeline. 

![](https://2047464521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBEa1hoX6SqpDj-ymNs%2Fuploads%2FvF11k2jp1GcmwFdWC4Pn%2Fimage.png?alt=media\&token=9c3e8f15-d6ea-4143-b15c-0e33c8af53ee)

3. **Pipelines:** Once you click on an application, it will redirect you to the **Pipelines** page. Click **+Create** button to [**create a new pipeline**](https://docs.opsmx.com/release-history/previous-releases/isd-4.0/knowledge-base/manage-pipelines/create-a-pipeline). Users can also view the existing pipelines displayed on the left.
4. **Click on** [**Add stage**](https://docs.opsmx.com/user-guide/manage-pipelines/add-stage)**:** The add stage button is displayed below the diagrammatic representation of the created pipeline. When you click this button, you can select the different types of stages that ISD supports.

<figure><img src="https://2047464521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBEa1hoX6SqpDj-ymNs%2Fuploads%2FVjOKgug5rsFwETIPKMSF%2Fadd%20stage%201.png?alt=media&#x26;token=fe443a49-3d5e-45c6-a003-b92c355a6bdf" alt=""><figcaption></figcaption></figure>

5. **Select Bake stage**: Select **Bake(Manifest)** stage from the drop-down menu. Baking an artifact allows you to use this artifact later in your spinnaker pipeline, without having to define its parameters.

<figure><img src="https://2047464521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBEa1hoX6SqpDj-ymNs%2Fuploads%2F5ZBCWoG4wxmI5ZVOfjP9%2Fhelmbased1.png?alt=media&#x26;token=e1e2211e-dd3c-4dee-b9c3-9eddb5c904e2" alt=""><figcaption></figcaption></figure>

6. **Configure Bake(Manifest):** Select the **Render engine** from the drop-down and provide the required details and then click **Save Changes** as shown in the image below.

<figure><img src="https://2047464521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBEa1hoX6SqpDj-ymNs%2Fuploads%2F5InpYczr71Yw2rt5oXxa%2Fhelmbased2.png?alt=media&#x26;token=ac95a29c-1c9b-4104-8b9f-c615ec3e9830" alt=""><figcaption></figcaption></figure>

* **Render Engine:** This is the engine used for rendering your manifest.
* **Helm name and namespace:** Defining the name and namespace specifies where in your cluster this artifact will deploy.
* **Expected Artifact:** Select the template you want to render.
* **Raw Overrides:** Use *--set* instead of *--set-string* when injecting override values. Values injected using *--set* will be converted to primitive types by Helm.
* **Expression Evaluation:** Explicitly evaluate SpEL expressions in overrides just prior to manifest baking. Can be paired with the "Skip SpEL evaluation" option in the Deploy Manifest stage when baking a third-party manifest artifact with expressions not meant for Spinnaker to evaluate as SpEL.

7. **Add your deployment stage**: Now that you have baked an object, you don’t have to define its parameters. Much like our steps to create a Kubernetes deployment guide, you can either add it as  [**text** ](https://docs.opsmx.com/release-history/previous-releases/isd-4.0/knowledge-base/manage-pipelines/execute-pipelines-run-deployments/deployment-to-kubernetes-namespace-with-manifest-file)or as an [**artifact**](https://docs.opsmx.com/release-history/previous-releases/isd-4.0/knowledge-base/manage-pipelines/execute-pipelines-run-deployments/deployment-to-kubernetes-namespace-with-git-based-manifest).
8. **Run your pipeline**: Verify to make sure that it works.