Menu
In the latest UI of spinnaker, there are projects and applications labels. What's the relationship between projects and applications in spinnaker?
360
An application in Spinnaker is a construct that represents some service that you are going to deploy (typically a microservice). It includes: the pipelines that process the service through to deployment in production. the infrastructure on which the service is run: clusters.
By pushing a Git tag that starts with “v”, we trigger Container Builder to build a new Docker image and push it to Container Registry. Spinnaker detects that the new image tag begins with “v” and triggers a pipeline to deploy the image to canaries, run tests, and roll out the same image to all pods in the deployment.
A pipeline is a sequence of stages provided by Spinnaker, ranging from functions that manipulate infrastructure (deploy, resize, disable) as well as utility scaffolding functions (manual judgment, wait, run Jenkins job) that together precisely define your runbook for managing your deployments.
Projects provide an aggregated view of a collection of applications, but that's about it. If you're only interested in a subset of applications managed by Spinnaker, it's a decent way to manage them.
The relationship is modeled as many-to-many: a project is made up of one or more applications, and applications can be part of multiple projects.
Being in a project doesn't affect the application in any way, beyond making it present in the project view. There are no notifications to be configured at the project level, or pipelines that span multiple applications. You can set up a project pretty quickly and easily to get an idea what the view looks like.
181
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
