Core Concepts
...
Pipelines
Steps
Deploy Application
4min
deploy an application to kubernetes to use this step, the application should already be deployed in the kubernetes cluster this step will re deploy your existing service syntax microtica yaml steps step name type deploy target kubernetes cluster my kubernetes cluster service my app tag v0 1 0 parameter description required title the display name of the step no type the type of the microtica built in step should always be deploy for this type of step yes target should always be kubernetes for this type of step yes cluster the name of the existing kubernetes cluster yes namespace deploy the application in a specific namespace default microtica no service the name of the existing application to be deployed yes tag docker image tag to be applied with the deployment default latest no branch filter if specified, deployment will be executed only if the pipeline was triggered by push on the matched branch otherwise, deployment will be triggered on every pipeline execution no re deploy an existing application we assume that application with name my app is already being deployed in the kubernetes cluster with name my cluster you can read more about how to create and deploy applications here in the following example we deploy a application on kubernetes with an image tag that’s previously been built and pushed to a remote docker registry microtica yaml steps clone type git clone pushdockerimage type docker push image name "microtica/my app" tag "{{mic pipeline execution id}}" deploy type deploy target kubernetes cluster my cluster service my app tag "{{mic pipeline execution id}}" to dynamically deploy the image that’s just been built, we use mic pipeline execution id as a reference value while pushing the image on a remote docker registry and use the same value when deploying the application trigger deploy for a specific branch to trigger a deploy only if the pipeline was triggered by push on a specific branch, we can use the branch filter parameter to achieve that basically, if you specify develop as a value, the deployment will be triggered only if push was made on the develop branch if branch filter is not specified, deploy will be triggered on each pipeline execution microtica yaml steps clone type git clone pushdockerimage type docker push image name "microtica/my app" tag "{{mic pipeline execution id}}" deploy type deploy target kubernetes cluster my cluster service my app tag "{{mic pipeline execution id}}" branch filter develop