skaffold run docs in Continuous Delivery pipeline
---
-title: "CI/CD with Skaffold"
-linkTitle: "CI/CD with Skaffold"
+title: "Continuous Delivery"
+linkTitle: "Continuous Delivery"
weight: 40
---
Skaffold offers several sub-commands for its workflows that make it quite flexible when integrating with CI/CD pipelines.
+
+## `skaffold run`
+
+`skaffold run` is a single command for a one-off deployment. It includes all the following phases as it builds, tags, deploys and waits for the deployment to succeed if specified.
+We recommend `skaffold run` for the simplest Continuous Delivery setup, where it is sufficient to have a single step that deploys from version control to a cluster.
+For more sophisticated Continuous Delivery pipelines, Skaffold offers building blocks that are described next:
+
+- health check - tell `skaffold deploy` or `skaffold run` to succeed only if all deployments are successful
+- `skaffold build` - build, tag and push artifacts to a registry
+- `skaffold deploy` - deploy built artifacts to a cluster
+- `skaffold render` - to export the transformed Kubernetes manifests for GitOps workflows
+
+## Waiting for Skaffold deployments using `healthcheck`
+
+{{< todo 1937 >}}
+
## `skaffold build | skaffold deploy`
`skaffold build` will build your project's artifacts, and push the build images to the specified registry. If your project is already configured to run with Skaffold, `skaffold build` can be a very lightweight way of setting up builds for your CI pipeline. Passing the `--file-output` flag to Skaffold build will also write out your built artifacts in JSON format to a file on disk, which can then by passed to `skaffold deploy` later on. This is a great way of "committing" your artifacts when they have reached a state that you're comfortable with, especially for projects with multiple artifacts for multiple services.
