# 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.
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.
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.
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.
* **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.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.opsmx.com/opsmx-1/opsmx-context-engine/user-guide/manage-pipelines/execute-pipelines-run-deployments/helm-based-deployment-to-kubernetes-namespace.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.