An application-level pipeline automates packaging and publishing for an entire application rather than for one service. It complements service pipelines when services change frequently but the application structure and deployment artifact change less often. section 3.6
Choose the pipeline boundary by considering:
- Whether services deploy individually or as a set. section 3.6
- How often services and application definitions change. section 3.6
- How many teams deploy the services and who consumes the artifacts. section 3.6
Conference application Helm Chart
A separate pipeline packages and publishes the Conference application Helm Chart. Teams can install the application with Helm, or render it with helm template and apply the output with kubectl. Service pipelines continue delivering the rapidly changing service code. section 3.6
Compare the different lifecycles of service pipelines and the application pipeline. section 3.6
