> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/isd-spinnaker/opsmx-intelligent-software-delivery-isd-platform-spinnaker/release-notes/additional-resources/previous-releases/isd-3.12/quickstart-guide/manage-pipelines/run-deployments-execute-pipelines/deployment-to-kubernetes-namespace-with-git-based-manifest.md).

# Deployment to Kubernetes namespace with Git based Manifest

A Kubernetes manifest is a text file that details a deployment. Deployment manifests however are usually stored in a repository like Github or bitbucket.

To deploy a manifest, from ISD:

1. **Go to Continuous Delivery**: When you log in to ISD you would start at the application dashboard, Click "**Continuous Delivery**" and then click "**Spinnaker**".  ISD primarily supports spinnaker applications and allows you to access your spinnaker instance directly from ISD’s UI to help save your team time.

![](/files/XZ4XuqCkqxrbMoXeCcGw)

2\.  Click on the application where you want to build this pipeline: On the spinnaker dashboard, you will see a list of recently opened applications and options to see all your applications or create a new application entirely. For the purposes of this tutorial, we are using the application **“Fresh tutorial”.**

![](/files/9l0zHkvSqPQAN6xMpI5B)

3\.  Once you click on an application, Click "**Pipelines**" navigate to the pipelines screen and then click "**Create**" button to create a new pipeline as shown in the image below.

![](/files/RaPAyWS7AIMHCFnMFGWd)

4\. **Create pipeline**: After clicking the "Create" button, you can create a new pipeline. You must name your pipeline. If you have an existing pipeline, you can copy it using the “**copy from**” feature and click "**Create**".

![](/files/ZxejKy1Yh6xWaXv6nQnd)

5\. Once you created the application, below screen will appear and click "**Configure**" button to add stage into your pipeline.

![](/files/f0i1Kg6gbz4d7USznBlS)

6\. **Click on “add stage”:** The add stage button is just under the diagrammatic representation of your pipeline. When you click this button, you can select many different types of stages that Spinnaker natively supports.

![](/files/m7zDqQ1P3VfJhjufuC4Q)

7\. **Select “Deployment”**: You can add a host of different stages using a drop down menu. They are all alphabetically sorted. Scroll down and select “**Deploy(Manifest)**”.

![](/files/lc9yHgalgDo1OsLNI1df)

8\. **Select your account**: An account is the name given to a kubernetes cluster.

![](/files/9IOK0s1PmhgacWSnyy3c)

9\. **Select your namespace**: A namespace is a specific address within a Kubernetes cluster, select the checkbox that says override namespace and you will be able to select the namespace in which your manifest will deploy.

![](/files/DuPPg5qJ5Rt7FpzovIhW)

10\. Define the file and the repository you are going to deploy the artifact from: Select "**Artifact**", and you will be prompted to select the repository which you are deploying from. In addition you must specify the **URL** of the artifact and the **branch** it is located in.

![](/files/NIuQXcgiRMGnor59U2oQ)

11\.  After updating the required details, Click on "**Save Changes**" to deploy the Git based manifest.