Spinnaker Architecture, CI/CD Practices, and Deployment Guide

Netflix is a benchmark for large‑scale production microservices and DevOps, and its open‑source Spinnaker project enables hybrid‑cloud deployments and continuous delivery pipelines.

Service Architecture : Spinnaker consists of multiple microservices such as Deck (frontend), Gate (API gateway), Orca (pipeline orchestration), Clouddriver (cloud provider interactions), Front50 (metadata), Rosco (image baking), Igor (CI integration), Echo (notifications), Fiat (authorization), Kayenta (canary analysis), and Halyard (lifecycle management).

Code Repository Management : Each microservice has its own GitHub repository, following a trunk‑based development model with dedicated release branches.

Continuous Integration : The CI pipeline uses GitHub Actions. The workflow file .github/workflows/build.yml defines a single job branch-build that runs on pushes to master or version‑* branches, sets Gradle options, checks out the code, configures Java 8 and 11, caches Gradle dependencies, and executes ./gradlew build . The full YAML content is shown below:

name: Branch Build

on:
  push:
    branches:
    - master
    - version-*

env:
  GRADLE_OPTS: -Dorg.gradle.daemon=false -Xmx2g -Xms2g

jobs:
  branch-build:
    if: startsWith(github.repository, 'spinnaker/')
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-java@v1
        with:
          java-version: 8
      - uses: actions/setup-java@v1
        with:
          java-version: 11
      - uses: actions/cache@v1
        with:
          path: ~/.gradle
          key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle') }}
          restore-keys: |
            ${{ runner.os }}-gradle-
      - name: Build
        run: ./gradlew -PenableCrossCompilerPlugin=true build --stacktrace

Application Deployment : Deploying Spinnaker can be complex due to external resource dependencies, but using pre‑downloaded assets reduces installation time to about 30 minutes. The version file (YAML) lists the Spinnaker version, each microservice’s version and commit hash, and required dependencies such as Redis, Consul, and Vault. The version field determines Docker image tags used by Halyard during deployment.

version: 1.19.4
services:
  echo:
    version: 2.11.2-20200401121252
  clouddriver:
    version: 6.7.3-20200401190525
  ... (other services omitted for brevity)

Running hal deploy apply triggers a one‑click deployment of the entire Spinnaker stack.

The article also suggests applying the same version‑controlled YAML approach to other microservice projects, enabling automated deployments and rollbacks via CI tools like Jenkins.

For readers interested in deeper Spinnaker practices, a promotional course link is provided at the end of the article.