# spinnaker Published articles for spinnaker. 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]() Original publisher: [Read original article]() Author: Nick Platt Published: 2023-02-20T12:24:46Z Content type: tutorial Language: en Sources: [Wise Engineering - Medium]() Topics: [argocd](), [spinnaker](), [CI/CD](), [GitOps](), [Kubernetes](), [Microservice](), [Deployment](), [Helm charts](), [Java]() Tags: [argo-cd](), [argocd](), [ci-cd](), [continuous-delivery](), [deployment](), [gitops](), [helm-charts](), [kubernetes](), [microservices](), [platform](), [spinnaker]() ### 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 ## GKE in production DevFeed: [GKE in production]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2017-07-02T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Gke](), [Google Cloud Platform (GCP)](), [Kubernetes](), [Amazon Web Services](), [Digital Ocean]() Tags: [aws](), [cloud-sql](), [digitalocean](), [gke](), [google-cloud](), [health-checks](), [heroku](), [ingress](), [kubernetes](), [postfix](), [sendgrid](), [spinnaker]() ### AI overview A developer describes deploying small applications on GKE and lessons learned from moving between AWS and Google Cloud. The article covers SSL with Kubernetes Ingress, email delivery through SendGrid, Cloud SQL access through a sidecar container, and deployment with a shell script or Spinnaker. ### Source excerpt I've been working with DigitalOcean, Heroku and AWS for some years now. ## How (and Why) We Moved to Spinnaker DevFeed: [How (and Why) We Moved to Spinnaker]() Original publisher: [Read original article]() Author: Target Brands, Inc Published: 2017-04-07T05:00:00Z Content type: article Language: en Sources: [Target]() Topics: [CI/CD](), [Cloud](), [Jenkins](), [Provisioning](), [Terraform](), [Microservices](), [Apache Cassandra](), [Persistence](), [Cache](), [Git]() Tags: [automation](), [cassandra](), [ci-cd](), [cloud](), [deployment](), [engineering](), [git](), [jenkins](), [microservices](), [redis](), [spinnaker](), [terraform]() ### AI overview Target describes moving portions of target.com from a homegrown cloud deployment platform to Spinnaker after evaluating CI/CD platforms. The team selected Spinnaker for its Jenkins integration, multi-cloud deployment support, and use of immutable images, then adapted its architecture with Terraform, cloud storage, and managed caching to support resilient, highly available operation. ### Source excerpt Background Just after the middle of last year, Target expanded beyond its on-prem infrastructure and began deploying portions of target.com to the cloud. The deployment platform was homegrown (codename Houston), and was backed wholly by our public cloud provider. While in some aspects that platform was on par with other prominent continuous deployment offerings, the actual method of deploying code was cumbersome and not adherent to cloud best practices. These shortcomings led to a brief internal evaluation of various CI/CD platforms, which in turn led us to Spinnaker. We chose Spinnaker because it integrates with CI tools we already use at scale (Jenkins), supports deploying to all major public cloud providers, and compels software deployment best practices - all deployments are performed via immutable images, a snapshot of config + code. Supporting a Platform The primary goal of Target's cloud platform is to enable product teams to deploy and manage their applications across multiple cloud providers. We provide CI/CD, monitoring, and service discovery as services, and any application deployed via our platform gets those capabilities via a base image that is pre-configured for connectivity to each service's respective endpoint. Since these components are essentially products we provide to internal customers, we had to ensure the new CD platform was operationally supportable and highly-available. So, as soon as we decided on Spinnaker, a handful of engineers from the Cloud Platform group set about making this happen. Default Spinnaker scripts make it easy to standup a single self-contained server with the microservices and persistence layer all together, but that wasn't conducive to doing blue-green deployments - allowing updates of Spinnaker without downtime to our internal customers. We built jobs for building packages based off the master branch of each Spinnaker component's upstream git repository, and wrote Terraform plans to manage the deployment of each stack. ## Target open-sources Winnaker to audit Spinnaker deployments DevFeed: [Target open-sources Winnaker to audit Spinnaker deployments]() Original publisher: [Read original article]() Author: Target Brands, Inc Published: 2017-02-13T06:00:00Z Content type: release Language: en Sources: [Target]() Topics: [Cloud](), [Tool](), [Continuous Delivery (CD)](), [Automation](), [Open Source](), [Deployment Strategies](), [Monitoring](), [Kubernetes]() Tags: [api](), [audit](), [automation](), [cloud](), [deployment](), [deployment-strategies](), [health-checks](), [identity-management](), [infrastructure](), [kubernetes](), [monitoring](), [open-source](), [platform](), [spinnaker](), [winnaker]() ### AI overview Target announces Winnaker, an open-source tool for auditing Spinnaker deployments from an end-user perspective. The article explains how Winnaker automates whole-system deployment testing and helps identify connectivity, API rate-limit, and infrastructure-configuration problems. ### Source excerpt Win the cloud with Winnaker! I am happy to announce that we, at Target, decided to open source a tool called Winnaker. This tool will allow the user to audit Spinnaker from an end user point of view. But first what is Spinnaker? The first time I heard the word Spinnaker, my reaction was, "wait, what does that even mean in English?" Shortly after, I found myself implementing a demo of Spinnaker as a potential replacement for our internal cloud deployment tool. Spinnaker is a cloud agnostic continuous delivery tool, which means we can push our code to any cloud provider we like. In fact, Spinnaker takes agnosticism to the next level by introducing three abstractions. Load balancers Server groups Security groups By enforcing this level of simplicity, it allows the implementation of deployment strategies such as Highlander, Red/Black on a vast different type of infrastructure (VM, Container, Kubernetes, public cloud, private cloud) with a high level of confidence and an incredible level of ease of use for the app developers. Spinnaker also roots for the immutable infrastructure design pattern. Baking your image once and deploying the image everywhere is another bold move that differentiates Spinnaker from the other tools. Why Winnaker ? Short answer is because of automation! Test the functionality of the CD system as a whole. Spinnaker has different components (CloudDriver, Rosco, Deck,...). Each of these components have their own unit tests and health checks that can be monitored. We learned the hard way that relying only on component health checks is not effective enough to ensure developers won't face any error when they deploy their apps. A few things can go wrong when off monitoring radar: Connectivity between the separate components Maxing out cloud provider API rate limit Base infrastructure configurations (subnet address space, identity management roles) So we decided to audit Spinnaker and cloud's whole functionality with a sample app. If baking and deploying our