> 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/troubleshooting-and-resources/armory/general/parameters-with-kubernetes-manifest-and-using-spel.md).

# Parameters with Kubernetes Manifest & Using SpEL

Question: How do I dynamically promote a build with parameters in a manifest file in Spinnaker using Kubernetes? Answer:

* The first step is to understand how to use parameters in your kubernetes manifest file. Here is a link to some good documentation: [Parameterize Kubernetes Manifests](https://www.spinnaker.io/guides/user/kubernetes-v2/parameterize-manifests/#parameterize-kubernetes-manifests)\* The second step is to create a pipeline expression to dynamically decide where to deploy the code based on some action. For our example we are using a manual judgement stage to determine if the code should go to Prod or Staging. Example: `Promote:${#judgement('Promote') == '' ? parameters['namespace'] : #judgement('Promote')}`

More Resources: If you would like to learn more about SpEL and Pipeline expressions with Spinnaker you can find it here: [Pipeline Expressions Guide](https://www.spinnaker.io/guides/user/pipeline-expressions/#pipeline-expressions-guide)