# spinnaker

Spinnaker is an open-source, multi-cloud continuous delivery platform for managing applications and releasing software changes.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## How Wise bootstraps Spinnaker using ArgoCD

DevFeed: [How Wise bootstraps Spinnaker using ArgoCD](<https://devfeed.tech/articles/how-wise-bootstraps-spinnaker-using-argocd-15455.md>)

Original publisher: [Read original article](<https://medium.com/wise-engineering/how-wise-bootstraps-spinnaker-using-argocd-2765e9373b61?source=rss----f2565bbe9c46---4>)

Author: Nick Platt

Published: 2023-02-20T12:24:46Z

Content type: tutorial

Language: en

Sources: [Wise Engineering - Medium](<https://devfeed.tech/sources/wise-engineering-medium.md>)

Topics: [argocd](<https://devfeed.tech/topics/argocd.md>), [spinnaker](<https://devfeed.tech/topics/spinnaker.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitOps](<https://devfeed.tech/topics/gitops.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Microservice](<https://devfeed.tech/topics/microservice.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Helm charts](<https://devfeed.tech/topics/helm-charts.md>), [Java](<https://devfeed.tech/topics/java.md>)

Tags: [argo-cd](<https://devfeed.tech/tags/argo-cd.md>), [argocd](<https://devfeed.tech/tags/argocd.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [continuous-delivery](<https://devfeed.tech/tags/continuous-delivery.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [helm-charts](<https://devfeed.tech/tags/helm-charts.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [platform](<https://devfeed.tech/tags/platform.md>), [spinnaker](<https://devfeed.tech/tags/spinnaker.md>)

### AI overview

Wise explains how it bootstrapped Spinnaker automatically with ArgoCD instead of using a staging Spinnaker to manage production. The article compares Spinnaker's pipeline-based deployment model with ArgoCD's declarative GitOps reconciliation model and describes using ArgoCD and its App of Apps pattern to manage Spinnaker installations across Kubernetes clusters.

### Source excerpt

Spinnaker and ArgoCD logos Deploying your deployment tool In our 2 part series, we discussed the state of our CI/CD systems and wrapped up with our vision for CD at Wise, and why we chose Spinnaker. Here's how we set up Spinnaker from scratch, overcoming the technical challenges of bootstrapping a CD platform. We wanted a hands-off and automated way to bootstrap Spinnaker. When researching across industry peers, one approach was to use a staging instance of Spinnaker to manage your production instance. This method of dual Spinnakers, wasn't viable for Wise, due to security concerns with a staging tool having access to change a production environment. It also meant accepting a potentially manual error prone process when managing your staging setup. Instead, we wanted to achieve a fully automatic installation for both of our Spinnaker environments and settled on using ArgoCD. Spinnaker & ArgoCD Spinnaker consists of around 11 Java microservices, which operates on a centralised deployment model -- push based deployments. It utilises pipelines heavily as its deployment strategy, which can be triggered via various input methods e.g. manual, artefact upload etc. Implementing deployments as pipelines allows engineers to describe a release as a set of steps, with powerful concepts such as canary analysis and quality gates built in. This is attractive for Wise, as use of standardised and reusable templates can enforce end consumers to follow a particular paved road e.g. canary deployments with automatic rollbacks. ArgoCD describes itself as "declarative GitOps for Kubernetes". It comprises fewer golang microservices and can be configured to be either centralised or decentralised. By default, ArgoCD differs by not utilising pipeline based deployments, instead operating via a GitOps reconciliation loop as its source of truth. Whatever is defined in Git, ArgoCD will try to reconcile within the cluster. ArgoCD is Kubernetes native and therefore can't be used for deploying infrast