Using the file_path option. In this case you provide your own Kubernetes manifest and Codefresh deploys it as-is. It is your
own responsibility to do custom replacements here (for example using awk, sed or yq). The deploy step is also using the Codefresh templating mechanism behind the scenes if you want to take advantage of it. For a full templating solution we also
suggest you look at Helm.
You need to define either one of these fields in the deploy step. If you define service you also can select the exact Docker image
with the candidate field (otherwise Codefresh will just reuse the docker image defined in the existing deployment)
The free-text display name of the step
A basic, free-text description of the step.
Parent group of this step. See using stages for more information.
Currently only kubernetes is supported
Name of your K8s cluster as found in the dashboard
Namespace where the deployment will take place
Name of the existing service that will updated. You need to provide service OR file_path
A deployment manifest. You need to provide service OR file_path
Seconds to wait for the deployment to be completed. Default is 120 seconds
Docker image that will be deployed. Only valid if service is defined. Should contain image and name of registry as it appears in the registry integration page.
If a step fails, and the process is halted. The default value is true.
Define a set of conditions which need to be satisfied in order to execute this step. You can find more information in the Conditional Execution of Steps article.