Understanding Skaffold pipeline stages
So far, we have built a basic understanding of how Skaffold works. From the previous chapters, we know that it picks source code changes in your project and creates container images with the tool of your choice; the images, once successfully built, are tagged as you see fit and pushed to the repository you specify. Skaffold also helps you deploy the artifacts to your Kubernetes cluster at the end of the workflow, once again using the tools you prefer.
Skaffold permits you to skip stages. If, for example, you run Kubernetes locally with Minikube or Docker desktop, Skaffold is smart enough to make that choice for you and will not push artifacts to a remote repository.
Let's look at Skaffold's pipeline stages in detail to understand what other choices we have in each pipeline stage. Skaffold pipeline stages can be broadly classified into the following areas:
- Init
- Build
- Tag
- Test
- Deploy
- File
- Log tailing...