A deployment pipeline automatically moves a tested component into production, avoiding manual command-line or GUI updates. This reduces delay, human error, and the effort of remembering deployment steps. section 5.5.2
A deployment can proceed in three steps:
- Package the component in a production-ready format, such as a container image, and publish it to a registry. section 5.5.2
- Configure production to use the updated component, triggering rollout and resource provisioning. section 5.5.2
- Wait until component instances are ready to handle production traffic. section 5.5.2
Figure 5.18 The deployment process consists of three steps: (1) the deployment pipeline publishes a component in a production ready package to a registry, (2) production is configured to use the updated component and (3) the component instances are started and become ready to handle production traffic
The diagram summarizes packaging and publishing, production configuration, and starting instances until they can handle traffic. section 5.5.2



