Spinnaker

AWS EC2 Launch Templates Setup

Mon, 01 Jan 0001 00:00:00 +0000

Please note that you should only proceed with this if you have AWS EC2 configured as a cloud provider. These features require 1.24 (although some features were launched in previous releases leading up to 1.24).

AWS uses launch templates to specify instance configuration information. Launch templates are the successor of launch configurations. This means that any new instance configuration feature from AWS will only be supported by launch templates.

Spinnaker still supports launch configurations for backwards compatibility, but recommends enabling launch templates to access any new features that AWS adds.

Canary Overview

Mon, 01 Jan 0001 00:00:00 +0000

Canary is a deployment process in which a change is partially rolled out, then evaluated against the current deployment (baseline) to ensure that the new deployment is operating at least as well as the old. This evaluation is done using key metrics that are chosen when the canary is configured.

Canaries are usually run against deployments containing changes to code, but they can also be used for operational changes, including changes to configuration.

Configuring the Script Stage

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

The Script stage lets you run an arbitrary shell, Python, or Groovy script on a Jenkins instance as a first class stage in Spinnaker. For example, you can use it to launch a test suite from a pipeline instead of doing it manually. Using the Script stage requires some additional setup after you add Jenkins to your Spinnaker deployment.

Prerequisites

To configure a Script stage, you need:

A running Jenkins instance at $JENKINS_HOST, with a Jenkins user profile set up with access to create jobs
A running Spinnaker instance, with access to configuration files, and in which you have set up Jenkins on Spinnaker

Configure Jenkins

Download the raw job xml config file with the command:

Enable Slack Support Channels

Mon, 01 Jan 0001 00:00:00 +0000

You can create an application and configure it with relevant data—application attributes.

Including a Slack support channel for an application is a configurable application attribute. This feature communicates with Slack’s conversations API to expose a list of available Slack channels in your workspace. The Slack support channel feature is supported by all providers.

Configuration

Gate

You need an API token associated with your Slack workspace for gate to receive a list of channels from Slack’s API. See the Slack documentation if you need to create a Slack token. Add this token in the config for gate’s encrypted secrets.

Get Started Using Spinnaker

Mon, 01 Jan 0001 00:00:00 +0000

This article assumes you are new to Spinnaker. It contains basic information about what to do after Spinnaker is installed .

Before you get going…

Whether you’re an operator or admin installing or managing Spinnaker or an end user getting started using Spinnaker, here are some pointers to get you started.

Operators (managing Spinnaker)

If you want to install Spinnaker, see the instructions here .
If you want to find out more about tuning and maintaining Spinnaker, here are some things to check out:

Google Compute Engine - Bakery

Mon, 01 Jan 0001 00:00:00 +0000

The GCE bakery configuration allows you to set the default network and zone and whether to use the public IP address of the VM used for baking the image.

For example, to set the default zone, add to the rosco-local.yml the following configuration

google:
  enabled: true
  bakery-defaults:
    zone: <zone>
    network: <network>
    networkProjectId: projectId
    subnetwork: subnetwork
    useInternalIp: <true|false>
    templateFile: gce.json
    baseImages:
    - id: unique-bake-id
      shortDescription: shortUI Description (aka precise)
      detailedDescription: Ubuntu precise
      packageType: rpm
      templateFile: gce.json
      osType: <defaults to Linux>
      customRepository: customRepoURL
      isImageFamily: // this is unique to google.

These base images are used to dynamically populate the bake stage UI:

Google Groups

Mon, 01 Jan 0001 00:00:00 +0000

Service account setup

In order to access a user’s group membership, we must use the Google Admin Directory API. We will setup a Google Cloud Platform (GCP) service account and grant it access to the Directory API.

Enable the Admin SDK here .
In your Cloud Console , create a service account that will access the G Suite Directory API.
1. Navigate to the “IAM & Admin” –> Service accounts section.
2. Click “Create Service Account.”
3. Give it a name like “spinnaker-fiat.”
4. Select “Furnish a new private key” and select the JSON format.
5. Select “Enable G Suite Domain-wide Delegation.”
6. Click “Create”, which should download the private key for your new service account (see figure below).
7. Transfer this JSON file to a known location in your Spinnaker deployment.
8. You should see your newly created service account in the list, along with “DwD” and an option to “View Client ID”. Click “View Client ID” (see figure below).
9. Note the Client ID displayed. It will be used in the next step.

LDAP

Mon, 01 Jan 0001 00:00:00 +0000

Please note that LDAP is flexible enough to offer lots of other options and configuration possibilities. Spinnaker uses the Spring Security libraries, which solve a number of challenges.

Configure fiat

With the LDAP manager credentials and search patterns in hand, add the following to fiat-local.yml

auth:
  group-membership:
    service: ldap
    ldap:
      url: ldaps://something.com
      managerDn: dn=something
      managerPassword: encrypted:secretPlease
      userSearchBase: searchBase
      groupSearchBase: ""
      ## optional, defaults to the uid={-},ou=users
      userDnPattern: uid={0},ou=users
      ## user search fitler defaults to null but could be set like so
      userSearchFilter: (employeeEmail={0})
      ## Defaults to uniqueMember={0}
      groupSearchFilter: (uniqueMember={0})
      ## defaults to cn
      groupRoleAttributes: cn
      groupUserAttributes: nullByDefault
      thresholdToUseGroupMembership: 100
      enablePagingForGroupMembershipQueries: false
      pageSizeForGroupMembershipQueries: 100
      loadUserDNsBatchSize: 100
      userIdAttribute: employeeEmail
      enableDnBasedMultiLoad: false
      cache:
        ## Defaults to false.  Enable to reduce LDAP load
        enabled: true
        expireAfterWriteSeconds: 600

See the ldap configuration code for more information on each setting.

Notifications and Events Guide

Mon, 01 Jan 0001 00:00:00 +0000

Out of the box, Spinnaker allows you to configure the following types of notifications:

This is discussed in the Configuring Notifications section below.

Additionally, Spinnaker allows you to set webhooks for git triggers. See the Setting up Git Triggers in Spinnaker section.

You can also set Spinnaker to stream all its events to a downstream listener. See the Add a Webhook to Spinnaker section.

Spinnaker is also capable of handling cron-based triggers and detect changes in Jenkins builds and Docker images by enabling continuous integration configuration in spinnaker

Oracle Cloud Infrastructure - Bakery

Mon, 01 Jan 0001 00:00:00 +0000

The Oracle Cloud Infrastructure (OCI) bakery configuration allows for setting the default availability domain, network, and instance shape of the VM used for baking the image. Add the following to rosco-local.yml to enable oracle account baking.

oracle:
  enabled: true
  bakery-defaults:
    availabilityDomain:
    subnetId:
    instanceShape:
    templateFile: oracle.json
    baseImages:
      baseImageId: 
      sshUserName: 
      packageType: rpm

These images are used to dynamically populate the bake stage UI:

Managed Delivery Overview

Mon, 01 Jan 0001 00:00:00 +0000

What is Managed Delivery?

Managed Delivery is an initiative with two key goals.

Provide native means for Spinnaker users to declaratively manage software delivery.
- With a declarative model, users describe the desired end-state of a deployed application. Spinnaker continually calculates how this desired state maps to cloud resources. When desired state diverges from actual cloud state, Spinnaker figures out how to safely bring the deployed state in-line with the desired.

Spinnaker Architecture Overview

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker microservices

Spinnaker is composed of a number of independent microservices:

Deck is the browser-based UI.
Gate is the API gateway.

The Spinnaker UI and all api callers communicate with Spinnaker via Gate.
Orca is the orchestration engine. It handles all ad-hoc operations and pipelines. Read more on the Orca Service Overview .
Clouddriver is responsible for all mutating calls to the cloud providers and for indexing/caching all deployed resources.
Front50 is used to persist the metadata of applications, pipelines, projects and notifications.

Pipeline Permissions

Mon, 01 Jan 0001 00:00:00 +0000

You can use pipeline permissions as an alternative to manually managing Fiat Service Accounts .

Without pipeline permissions, a Spinnaker operator first has to create a Fiat Service account with the correct permissions. A user can then specify the service account as the RunAsUser per automated trigger. Pipeline permissions simplifies this flow – a user only has to specify the set of roles in the pipeline specification based on which a Fiat service account is automatically created and associated with the pipeline.

Plugin Creators Overview

Mon, 01 Jan 0001 00:00:00 +0000

The contents of this page refer to alpha features in Spinnaker 1.19.4.

This means we are working on their stability and usability, as well as possibly adding or changing features. Expect rough edges, and file issues as needed.

Requirements

Spinnaker v2025.3.0+

Taxonomy

Extension Point: Defined by a Spinnaker service, it represents an official contract for which extensions can be written against. Defined by using an org.pf4j.ExtensionPoint interface. Written by Core Contributors.

SAML

Mon, 01 Jan 0001 00:00:00 +0000

The SAML use case is a special one - it’s the only one where a user’s roles cannot be dynamically updated. This is because the user’s roles are sent in the initial authentication handshake between Gate and the SAML Identity Provider (IdP).

IdP Setup

To enable SAML roles, configure your IdP to include group membership in the assertion (not covered - some providers may not offer this option). By default, Gate looks for the memberOf attribute statement, but this can be reconfigured in Gate’s settings.

Service Accounts

Mon, 01 Jan 0001 00:00:00 +0000

Service Accounts enable the ability for automatically triggered pipelines to modify resources in protected accounts or applications. Practically speaking, this means that a Git commit could trigger a Jenkins build that could then kick off a pipeline to deploy the newly built image in your access-controlled QA environment. The pipeline would run utilizing the permissions of the service account. Service accounts are NOT authenticated accounts but abstractions around permissions for roles.

API Rate Limiting

Mon, 01 Jan 0001 00:00:00 +0000

If your Spinnaker deployment has API clients interacting with it, enabling and knowing how to operate the API rate limiter can help keep Spinnaker reliable through spikes of heavy traffic or rogue clients.

Intro

The API Rate Limiter currently supports limiting individual authenticated and anonymous principals, bucketing requests into windows that are refreshed every interval as well as global & per-principal learning mode. Both the capacity, as well as the window size, are configurable globally and per-principal.

AWS EC2 Launch Templates

Mon, 01 Jan 0001 00:00:00 +0000

Launch Template Support must be enabled in order to use the features described in this page. Follow guidelines here to enable the feature set.

Note: The features supported in the UI (Deck) come with tool tips that can help you learn the new features. Consider trying them out in Deck, especially if they are new to you.

Feature Configuration

Once launch templates support is enabled in Clouddriver, a new set of features are unlocked. Some of them are tied to the EC2 launch template directly like IMDSV2 and others require a launch template to be used in order to support features like SpotAllocationStrategy ( MixedInstancesPolicy features).

Caching: Account Name Based Sharding

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Account name based sharding is applicable to the caching function of a clouddriver. In case of HA mode, it is applicable to clouddriver-caching pods only. This feature is added at caching scheduler(both redis & sql backed) level which means it’s applicable to any cloud provider.

This is a configurable feature. When configured, all the caching agents of an account are run by a single caching pod. The logic of identifying the account whose caching agents are to be run in a particular pod is dependent on the name of the account(hashcode) and the number of available caching pods. When the pods are scaled up or down, the agents will resettle to the same or a different pod based on the sharding logic.

Configure a canary

Mon, 01 Jan 0001 00:00:00 +0000

Before you can add a canary stage to a pipeline, you need to configure what the canary consists of, including:

A name by which a canary stage can choose this config
The specific metrics to evaluate, and a logical grouping of those metrics
Default scoring thresholds (which can be overridden in the canary stage)
Optionally, one or more filter templates

Canary configuration is done per Spinnaker application . For each application set up to support canary, you create one or more configs.

Configure an application

Mon, 01 Jan 0001 00:00:00 +0000

Once you’ve created an application , you can finish configuring it before adding infrastructure and pipelines.

Start configuring

From within the application, click CONFIG at the top right of the Spinnaker screen.

The application attributes you defined when you created the app are shown at the top.

Note Spinnaker can infer applications based on existing infrastructure. In these cases, there are no application attributes. For applications that you want to use as applications (as described in this guide) you’ll have to add the attributes.

Create an application

Mon, 01 Jan 0001 00:00:00 +0000

You can’t create a deployment pipeline unless you have an application to put it in. If you’re accessing Spinnaker for the first time and there are no applications available, the first thing you’re going to do is create one.

From any screen, click on the Applications tab.

Note that there might be some applications there already. In some cases, Spinnaker creates applications automatically based on existing infrastructure.

These applications will be marked “unconfigured”; they won’t have the application attributes that are added when you create a new application. These inferred applications are not suitable for putting your pipelines in; go ahead and create a new one.

Custom CAs for Webhooks

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Webhook stages enable Spinnaker to make HTTP(S) calls to external web services. If the configured webhook URL has the https:// scheme, Spinnaker will use TLS to communicate with the external server. Spinnaker will attempt to validate the certificate presented by the server by building a chain of trust back to a trusted certification authority (CA) and will refuse to connect if the certificate cannot be validated.

By default Spinnaker uses the trust store provided by the JVM as its source of trusted CAs. The default behavior is sufficient for webhooks to public-facing servers where it is possible to build a chain of trust back to a root CA. Internal servers, however, may have certificates issued by a company-specific CA that is not trusted by a root CA. Webhooks to these servers over https:// will fail using the default configuration.

Custom Job Stages

Mon, 01 Jan 0001 00:00:00 +0000

For users of Kubernetes or Titus, Custom Job Stages offer a native solution for enhancing Spinnaker’s functionality with the power of containers. Custom Job Stages enable operators to extend Spinnaker without having to maintain a custom build of Orca.

Note: Custom Job stages are only supported for the Kubernetes and Titus providers.

How it works

At its core, Custom Job Stages use the Run Job stage to start a Task (Titus) or Job (Kubernetes) to perform some type of work. These jobs are defined as configuration for Orca and registered when the application starts. When used in a pipeline, Orca takes this configuration, generates a Run Job stage and then executes it. To support a more native experience, we provide configuration options for things like stage name, description and parameters so that this stage feels less like a Run Job stage and more like an out of the box stage.

Custom Webhook Stages

Mon, 01 Jan 0001 00:00:00 +0000

Custom webhook stages provide a simple, yet powerful, way of adding custom stages to Spinnaker. These stages are typically used to make quick API calls to an external system as part of a pipeline. Instead of extending the various components through code, users can simply add configuration to Orca for these stages. They appear in the UI as if they were a native stage.

Creating a Custom Webhook Stage

To set up a custom webhook stage, you’ll need to modify the orca-local.yml configuration file. The webhook.preconfigured property allows you to define multiple webhook stages. Here’s an example configuration:

Delete an application

Mon, 01 Jan 0001 00:00:00 +0000

If you have any server groups in this application, you need to delete them first.
From the Applications screen, open the application you want to delete.
Click CONFIG.
Scroll to the bottom of the application configuration screen, and click Delete Application.

Echo: Cassandra to In-Memory

Mon, 01 Jan 0001 00:00:00 +0000

Echo’s scheduler can be run completely in-memory. On startup or redeploy, echo will check cron schedules to see if it needs to retroactively execute any missed triggers. This migration only requires configuration changes.

1. Disable Cassandra in echo.yml

spinnaker:
  cassandra:
    enabled: false

2. Enable in-memory backend in echo.yml

spinnaker:
  inMemory:
    enabled: true

3. Enable the scheduler compensation job in echo.yml

scheduler:
  compensationJob:
    enabled: true
    windowMs: 1800000 # optional

The windowMs property dictates how far in the past echo will look to find missed schedules. By default this is 30 minutes.

Create and use filter templates

Mon, 01 Jan 0001 00:00:00 +0000

Filter templates allow you to compose and parameterize advanced queries against your telemetry provider. Parameterized queries are hydrated by values provided in the canary stage .

Things to keep in mind

Each filter template you create for a given canary configuration is available to each individual metric you add.
The query against your metrics is the metric type plus selectors that refine what is returned in the time series.

For Spinnaker canary purposes, the filter template contains only those refining selectors. The metric type is provided by the list of metrics above.

Front50: Cassandra to Object Store (S3, Azure, or GCS)

Mon, 01 Jan 0001 00:00:00 +0000

Cassandra is no longer an actively maintained or supported persistence store.

A migration to S3, GCS, or AZS is recommended.

1. Create a bucket and folder

Make up a bucket name (or account name if using Azure) that is consistent with the naming policies for the underlying storage service. For purposes of this document, we’ll pick ${USER}-spinnaker since many storage services (including Amazon S3, Google GCS, and Azure AZS) require globally unique names.

Front50: Cassandra to Redis

Mon, 01 Jan 0001 00:00:00 +0000

1. Install Redis

2. Disable Cassandra in front50.yml

cassandra:
  enabled: false

3. Enable Redis in front50.yml

spinnaker:
  redis:
    enabled: true

4. Export existing applications, pipelines, strategies, notifications and projects

#!/bin/sh

rm applications.json
curl http://FRONT50_HOSTNAME:FRONT50_PORT/global/applications | json_pp > applications.json

rm pipelines.json
curl http://FRONT50_HOSTNAME:FRONT50_PORT/pipelines | json_pp > pipelines.json

rm strategies.json
curl http://FRONT50_HOSTNAME:FRONT50_PORT/strategies | json_pp > strategies.json

rm notifications.json
curl http://FRONT50_HOSTNAME:FRONT50_PORT/notifications | json_pp > notifications.json

rm projects.json
curl http://FRONT50_HOSTNAME:FRONT50_PORT/v2/projects | json_pp | jq '._embedded.projects' > projects.json

5. Deploy new Front50

6. Import applications, pipelines, strategies, notifications and projects

#!/bin/sh

curl -X POST -H "Content-type: application/json" --data-binary @"notifications.json" http://FRONT50_HOSTNAME:FRONT50_PORT/notifications/batchUpdate
curl -X POST -H "Content-type: application/json" --data-binary @"strategies.json" http://FRONT50_HOSTNAME:FRONT50_PORT/strategies/batchUpdate
curl -X POST -H "Content-type: application/json" --data-binary @"pipelines.json" http://FRONT50_HOSTNAME:FRONT50_PORT/pipelines/batchUpdate
curl -X POST -H "Content-type: application/json" --data-binary @"applications.json" http://FRONT50_HOSTNAME:FRONT50_PORT/global/applications/batchUpdate
curl -X POST -H "Content-type: application/json" --data-binary @"projects.json" http://FRONT50_HOSTNAME:FRONT50_PORT/v2/projects/batchUpdate

Getting Set Up for Spinnaker Development

Mon, 01 Jan 0001 00:00:00 +0000

Overview

This page describes the steps a Developer should take to fetch Spinnaker’s codebase and get set up to work on it.

Follow the contributing guidelines if you plan to submit your work as a patch to the open source project.

System Requirements

This guide assumes you have access to a machine with a minimum specification of:

At least 16 GB of RAM
At least 6 cores CPU

MacOS

These are some tools but install additional as needed the tools for your needs

Hiding Stages

Mon, 01 Jan 0001 00:00:00 +0000

Stages that are not provider-specific will be available by default. To hide specific stages from end-users, set the hiddenStages property in Deck’s settings-local.js to a list of the keys of stages you wish to hide. For example, to hide the Gremlin and Travis stages, include the following in settings-local.js:

 window.spinnakerSettings.hiddenStages = ['gremlin', 'travis'];

Kubernetes CRD Extensions

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker Extension Points for Custom Resource Definitions

At Google, we’ve built extension points for deep CRD integrations within Spinnaker.

This work has allowed us to support the following features within Spinnaker:

Custom models for representing CRDs as spinnakerKinds
Deploying CRDs with custom Spinnaker artifact types
Custom Kubernetes API versions
Custom Spinnaker naming strategies
Per-account, custom Spinnaker UIs that can run alongside the existing Kubernetes UIs

This guide is for developers who want to duplicate this functionality for their CRDs. It also exists as an explanation of certain code paths within Spinnaker which include hooks with no current corresponding open-source implementations.

Manage Applications

Mon, 01 Jan 0001 00:00:00 +0000

Overview

spin can manage the whole lifecycle of your application:

$ spin application

Usage:
   application [command]

Aliases:
  application, applications, app

Available Commands:
  delete      Delete the specified application
  get         Get the specified application
  list        List the all applications
  save        Save the provided application

Flags:
  -h, --help   help for application

Global Flags:
      --config string          path to config file (default $HOME/.spin/config)
      --gate-endpoint string   Gate (API server) endpoint (default http://localhost:8084)
  -k, --insecure               ignore certificate errors
      --no-color               disable color (default true)
      --output string          configure output formatting
  -q, --quiet                  squelch non-essential output

Use " application [command] --help" for more information about a command.

The following assumes Spinnaker is running and Gate is listening on http://localhost:8084. If gate is running elsewhere, you can set the Gate endpoint with the global --gate-endpoint flag.

Manage Canary Configs

Mon, 01 Jan 0001 00:00:00 +0000

Overview

$ spin canary canary-configs
Usage:
   canary canary-config [command]

Aliases:
  canary-config, canary-configs, cc

Available Commands:
  delete      Delete the provided canary config
  get         Get the canary config with the provided id
  list        List the canary configs
  retro       Retro the provided canary config
  save        Save the provided canary config

Flags:
  -h, --help   help for canary-config

Global Flags:
      --config string            path to config file (default $HOME/.spin/config)
      --default-headers string   configure default headers for gate client as comma separated list (e.g. key1=value1,key2=value2)
      --gate-endpoint string     Gate (API server) endpoint (default http://localhost:8084)
  -k, --insecure                 ignore certificate errors
      --no-color                 disable color (default true)
      --output string            configure output formatting
  -q, --quiet                    squelch non-essential output

Use " canary canary-config [command] --help" for more information about a command.

The following instructions assume Spinnaker is running and Gate is listening on http://localhost:8084. If gate is running elsewhere, you can set the Gate endpoint with the global --gate-endpoint flag.

Manage Pipeline Templates

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Note: spin only supports pipeline templates v2.

spin can manage the whole lifecycle of your v2 pipeline templates:

$ spin pipeline-templates

Usage:
   pipeline-template [command]

Aliases:
  pipeline-template, pipeline-templates, pt

Available Commands:
  delete      Delete the provided pipeline template
  get         Get the pipeline template with the provided ID
  list        List the pipeline templates for the provided scopes
  plan        Plan the provided pipeline template config
  save        Save the provided pipeline

Flags:
  -h, --help   help for pipeline-template

Global Flags:
      --config string          path to config file (default $HOME/.spin/config)
      --gate-endpoint string   Gate (API server) endpoint (default http://localhost:8084)
  -k, --insecure               ignore certificate errors
      --no-color               disable color (default true)
      --output string          configure output formatting
  -q, --quiet                  squelch non-essential output

Use " pipeline-template [command] --help" for more information about a command.

The following assumes Spinnaker is running and Gate is listening on http://localhost:8084. If gate is running elsewhere, you can set the Gate endpoint with the global --gate-endpoint flag.

Manage Pipelines

Mon, 01 Jan 0001 00:00:00 +0000

Overview

spin can manage the whole lifecycle of your pipeline:

$ spin pipeline

Usage:
   pipeline [command]

Aliases:
  pipeline, pipelines, pi

Available Commands:
  delete      Delete the provided pipeline
  execute     Execute the provided pipeline
  get         Get the pipeline with the provided name from the provided application
  list        List the pipelines for the provided application
  save        Save the provided pipeline

Flags:
  -h, --help   help for pipeline

Global Flags:
      --config string          path to config file (default $HOME/.spin/config)
      --gate-endpoint string   Gate (API server) endpoint (default http://localhost:8084)
  -k, --insecure               ignore certificate errors
      --no-color               disable color (default true)
      --output string          configure output formatting
  -q, --quiet                  squelch non-essential output

Use " pipeline [command] --help" for more information about a command.

The following assumes Spinnaker is running and Gate is listening on http://localhost:8084. If gate is running elsewhere, you can set the Gate endpoint with the global --gate-endpoint flag.

Next Release Preview

Mon, 01 Jan 0001 00:00:00 +0000

Please make a pull request to describe any changes you wish to highlight in the next release of Spinnaker. These notes will be prepended to the release changelog.

Coming Soon in Release 2026.3.0

Breaking Changes

AWS V2 SDK migration

The caching agents and code have been moved to the AWS V2 SDK. Any V1 usage via plugins or similar will no longer work going forward.

Angular removed

Angular has been removed from the Spinnaker project. For any plugins or forks, please migrate to React. This is a substantial migration — a big thank you to the contributors, primarily Matt Gogerly.

Orca: Quality of Service

Mon, 01 Jan 0001 00:00:00 +0000

EXPERIMENTAL: This feature is still in an early adoption / experimental phase. While you can use it today (Orca v6.71.0), Netflix is currently running this in learning mode / judiciously enabling in response to on-call events.

Spinnaker ships with an optional Quality of Service (QoS) module that can be used to manage the amount of active executions running at any given time. By default, this QoS module is disabled, but can be enabled and tuned with a handful of knobs and different strategies. Before we dive into the configuration settings, we’ll go over how QoS works.

Orca: Redis to SQL Migration

Mon, 01 Jan 0001 00:00:00 +0000

If you are not migrating an existing Orca deployment, refer to Orca SQL Setup instead.

Migrate from Redis to SQL

Migrating without downtime from Redis to SQL is a three-step process:

When DualExecutionRepository is running, writes will be routed to either Redis or SQL. Executions will only be migrated to SQL once they’ve completed (either successfully or terminally): This keeps the migration story simple. As such, the migration agents will need to run for awhile. At Netflix, we ran the migration cluster for two weeks, as we had long pipeline executions due to canaries. You may only need to run the migration cluster for an hour.

Orca: Zombie Executions

Mon, 01 Jan 0001 00:00:00 +0000

Aliases: orphaned execution

A zombie Execution is one that has a status in the database of RUNNING but there are no messages in Orca’s work queue or unacked set—the pipeline or task is not doing anything.

Diagnosis

Logs will be emitted regularly for Executions that are currently running in Orca via the QueueProcessor class, which will look similar to the following example. If no logs have been emitted for over 10 minutes for a RUNNING Execution, it is very likely a zombie.

Releasing A Patch

Mon, 01 Jan 0001 00:00:00 +0000

Say you’ve written a patch, and it’s been merged into Spinnaker. First off, thanks for helping the project! Odds are, you want to deploy this patch to the Spinnaker you manage. You have a few options available:

Wait for the non-patch release

Any time we release a new minor version of Spinnaker (e.g. 1.16.0 or 1.17.0), we include all commits merged into main for each service. We do this on a quarterly basis by default.

Sharding Spinnaker

Mon, 01 Jan 0001 00:00:00 +0000

Intro

This document shows you how to shard traffic to different Spinnaker services based upon configured criteria. The general pattern is to define a selector class in your configuration. Endpoints will then be selected based upon the criteria specified in the selectors.

As an example, Netflix creates read-only shards for Clouddriver to better manage requests.

Selectors exist at these levels:

Application
Execution type (i.e, Pipeline vs Orchestration)
Origin
Authenticated User
Deployment account
Cloud Provider

You will need to modify your Spinnaker deployment pipelines to ensure the infrastructure for each shard is correctly created, otherwise traffic could be sent to non-existent shards.

Usage Statistics

Mon, 01 Jan 0001 00:00:00 +0000

If enabled , Spinnaker collects data about how the tool is being used. This data is anonymized (before being sent across the internet) and aggregated.

Why is data being collected?

The project maintainers have few signals about how the product is actually being used in the real world.

Is new feature X having any traction with users? Can we remove feature Y because it’s hard to maintain?

Questions like these are difficult to answer without at least some automated data collection, and ultimately that leads to a product that becomes slow, bloated, and littered with failed experimental code that nobody is confident about deleting.

Writing a New Stage

Mon, 01 Jan 0001 00:00:00 +0000

Overview

To create a new stage, you need to make changes in the monorepo to orca to implement the logic of the stage, and the front-end changes in deck to implement the UI. Depending on what the stage does, you may need to implement new cloud provider-specific logic in clouddriver and/or expose new APIs in gate as well.

This doc currently only covers the backend changes made to orca.

Backend (orca)

For the backend, you need to define:

Getting Started as a Content Contributor

Mon, 01 Jan 0001 00:00:00 +0000

Originally published on the Spinnaker Community Blog

Hi! Nikema here. I co-lead the Spinnaker Contributor Experience Special Interest Group (SIG) with Adetokunbo Ige. Since stepping into this role, I’ve wanted to write a post to explicitly welcome non-code contributions to the project. This is meant to be a living document, and I am open to feedback and suggestions. Let’s work together to make open source contributing a little less intimidating.

I will be loosely referring to contributing to Spinnaker, but I intend to make this a starting point for anyone new to content contributing.

Enable Pipeline Templates

Mon, 01 Jan 0001 00:00:00 +0000

hal config features edit --pipeline-templates true
hal deploy apply

Getting Started

Mon, 01 Jan 0001 00:00:00 +0000

This means that we support only EC2 and Titus, and that we have limited feature and UI support. This guide walks through onboarding to Managed Delivery assuming that you are using EC2 or Titus.

Intro

To get started with Managed Delivery you’ll need an idea of what infrastructure you want to manage. You can pick a new piece of infrastructure that you want to create (a new load balancer, for example) or migrate an existing piece of infrastructure (an existing cluster, for example).

API

Mon, 01 Jan 0001 00:00:00 +0000

The endpoints for managed delivery are located in the managed-controller. The endpoints are easily accessible from the swagger api page of your Spinnaker instance.

This doc provides samples for how to use the endpoints.

Export an Existing Resource

The export endpoint (under the “managed-controller”) allows you to take an existing resource and export it to a yaml config.

GET /managed/resources/export/{cloudProvider}/{account}/{type}/{name}?serviceAccount=yourServiceAccount@company.com

These definitions can be stored in your git repo.

Validating yaml

The ad-hoc diff endpoint allows you to see if a resource config is valid, and to see the difference between config (desired state) and reality.

Managed Delivery Artifacts

Mon, 01 Jan 0001 00:00:00 +0000

Managed Delivery supports two types of delivery artifacts: debians and Docker images.

Delivery artifacts are meant to provide Spinnaker information about:

Where to locate the available versions of an artifact you care about
How to choose the latest version from a list of versions

Spinnaker needs this information to make decisions about when and how to roll out new versions as they become available. Artifacts are defined with name, type, and version strategy information.

Choose your Environment

Mon, 01 Jan 0001 00:00:00 +0000

In this step, you choose where to install Spinnaker. The recommended path is an installation into a Kubernetes cluster

Kubernetes installation

Each of Spinnaker’s microservices services are deployed separately. This is highly recommended for use in production.
Local installations of Debian packages

You can also install on a single local machine, or for Spinnaker development, making sure you have the 4 cores and 16GB in each case.

Spinnaker is deployed on a single machine. This is ok for smaller Spinnaker deployments, but Spinnaker will be unavailable when it’s being updated. Note it’s often better to use a microk8s/k3s installation to deploy rather than try to deploy a local debian.

Create a Pipeline Template

Mon, 01 Jan 0001 00:00:00 +0000

When you create a pipeline template, you start with the underlying JSON of a pipeline that already resembles the template you want. You turn this JSON into template JSON.

1. Get a pipeline’s JSON

Use spin CLI to get the JSON of an existing pipeline that is close to what your template will be. Alternatively, you can create a new pipeline in the model of your intended template.

Install the spin CLI , if you haven’t already done so.

Delivery Configs

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisite: read and complete the Getting Started document!

What is a Delivery Config?

A delivery config allows you to group resources together in a single file (e.g. spinnaker.yml) and specify how these resources work together to promote an artifact between environments.

Artifacts

An artifact represents the package or docker image that you want to promote in your delivery flow. For example, if you develop the package keeldemo (which is built into a debian) and that is the only package that runs in your application, you’d have the following artifact section:

Environment Constraints

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisite: understand the environment concept offered by Delivery Configs

What is an Environment Constraint?

Environment constraints control how an artifact version flows through environments. A constraint can be as simple as ensuring an artifact isn’t promoted into Environment B unless it has successfully deployed into Environment A. Constraints can also specify that an artifact needs to have a canary evaluated by Kayenta before it can be deployed into an environment, while also defining how the canary should be deployed and evaluated.

Git-Based Workflows

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker supports git-based workflows to create and update Managed Delivery configurations. This allows you to keep your Managed Delivery configuration in code and follow all the usual best practices like code review and approvals before a change is introduced to your managed resources, environments or deployments.

Git support is currently achieved via a pipeline configured with a trigger that can provide source repository information (such as a Git trigger) and containing a single Import Delivery Config stage. This stage will retrieve a Delivery Config manifest from the repository associated with your pipeline’s trigger, then save (or update) it in Spinnaker so it will automatically monitor and manage the resources, environments and deployments described in the manifest.

Mark an Artifact as Bad

Mon, 01 Jan 0001 00:00:00 +0000

You can mark a version of an artifact in an environment as bad to ensure that that version never gets deployed to the environment. If you mark an artifact as bad in the first in a series of environments (linked together by depends-on constraints) that version of the artifact will never be promoted into the later environments.

Marking via the API

To mark the artifact via the API you’ll need the application name, the name of the environment, the reference for your artifact (defined in your delivery config, defaulted to the artifact name), and the version that is bad. The request needs to have a body that contains this information . Here’s an example:

Pin an Environment

Mon, 01 Jan 0001 00:00:00 +0000

You can pin an environment to a specific artifact version to ensure that all resources in the environment stay on that version. Until the pin is removed, that environment won’t change to a new version of the artifact.

Pinning via the API

To create a pin via the API you’ll need the application name, the name of the environment you want to pin, the reference for your artifact (defined in your delivery config, defaulted to the artifact name), and the version you’d like to pin to. The request needs to have a body that contains this information . Here’s an example:

pf4jStage Plugin Deployment Example

Mon, 01 Jan 0001 00:00:00 +0000

Overview

_Note: Spinnaker supports plugins with both server and frontend components.

In this guide, you deploy the pf4jStagePlugin plugin from the spinnaker-plugin-examples repository.

By implementing Orca’s SimpleStage PF4J extension point, the pf4jStagePlugin creates a custom pipeline stage that waits a random number of seconds before signaling success. This plugin consists of a random-wait-orca Kotlin server component and a random-wait-deck React UI component that uses the rollup.js plugin library.

Requirements

This guide was tested with the following software versions:

Resource Status

Mon, 01 Jan 0001 00:00:00 +0000

If you’re not sure what a managed resource is, check out our Overview of Managed Delivery first.

Overview

Managed resources always have a status, which describes the current state of the resource from Spinnaker’s perspective. A resource’s status can help you quickly answer questions like:

Is Spinnaker taking automatic action on this resource right now?
Does the actual state of this resource match the declarative configuration I gave to Spinnaker?
Is something wrong with this resource?

How to find a resource’s status

UI

On the Infrastructure views (Clusters, Load Balancers, Firewalls), you’ll see a color-coded “M” logo attached to any resources that are managed by Spinnaker. Hovering over the logo reveals additional context about the current status and what it means.

Inherit from a Template or Override It

Mon, 01 Jan 0001 00:00:00 +0000

In a pipeline that instantiates a template, besides providing values for template variables you can…

Inherit features from the template
Override (add to) inherited features.

Inherit from the template

By default, the pipeline instance inherits the stages, expected artifacts, triggers, parameters, and notifications from the template. It’s possible to opt out of inheriting triggers, parameters, and notifications by including the corresponding string in the exclude element.

For example, the template might have a trigger defined in the triggers element, but you can opt out of inheriting it by including triggers inside the exclude element.

Create a Pipeline from a Template

Mon, 01 Jan 0001 00:00:00 +0000

Given a pipeline template that defines variables to be resolved per pipeline, you can create pipelines that reference that template and that provide values for all of those variables.

Instantiate a pipeline

Get the pipeline template.

spin pipeline-template list

This returns a list of all pipeline templates available in the Spinnaker deployment.
From the list, determine which of the listed templates is the one you want, and get it using the following command:

Deploy Spinnaker and Connect

Mon, 01 Jan 0001 00:00:00 +0000

Now that we’ve enabled one or more Cloud Providers , picked a Deployment Environment , and configured Persistent Storage , we’re ready to pick a version of Spinnaker, deploy it, and connect to it.

Pick a version

See the available versions on the versions page

You can follow the links to the versions’ respective changelogs to see what features each adds.
Set the version you want to use: Set this on the kustomize image tag configuration . All spinnaker versions since the monorepo use the same image tags, e.g. 2025.3.2.

Install and Configure Spin CLI

Mon, 01 Jan 0001 00:00:00 +0000

For more information, see the spin CLI Guide

Install `spin`

One way to manage applications and pipelines as code is through spin .

To acquire spin, do the following:

On Linux

curl -LO https://storage.googleapis.com/spinnaker-artifacts/spin/$(curl -s https://storage.googleapis.com/spinnaker-artifacts/spin/latest)/linux/amd64/spin

chmod +x spin

sudo mv spin /usr/local/bin/spin

On MacOS

# Apple Silicon
curl -LO https://storage.googleapis.com/spinnaker-artifacts/spin/$(curl -s https://storage.googleapis.com/spinnaker-artifacts/spin/latest)/darwin/arm64/spin
# Intel
curl -LO https://storage.googleapis.com/spinnaker-artifacts/spin/$(curl -s https://storage.googleapis.com/spinnaker-artifacts/spin/latest)/darwin/amd64/spin

chmod +x spin

sudo mv spin /usr/local/bin/spin

On Windows

New-Item -ItemType Directory $env:LOCALAPPDATA\spin -ErrorAction SilentlyContinue

Invoke-WebRequest -OutFile $env:LOCALAPPDATA\spin\spin.exe -UseBasicParsing "https://storage.googleapis.com/spinnaker-artifacts/spin/$([System.Text.Encoding]::ASCII.GetString((Invoke-WebRequest https://storage.googleapis.com/spinnaker-artifacts/spin/latest).Content) -replace "`n")/windows/amd64/spin.exe"

Unblock-File $env:LOCALAPPDATA\spin\spin.exe

$path = [Environment]::GetEnvironmentVariable("PATH", [EnvironmentVariableTarget]::User) -split ";"
if ($path -inotcontains "$env:LOCALAPPDATA\spin") {
  $path += "$env:LOCALAPPDATA\spin"
  [Environment]::SetEnvironmentVariable("PATH", $path -join ";", [EnvironmentVariableTarget]::User)

  $env:PATH = (([Environment]::GetEnvironmentVariable("PATH", [EnvironmentVariableTarget]::Machine) -split ";") + $path) -join ";"
}

Configure `spin`

spin reads its configuration from ~/.spin/config.

Visualize a Hydrated Pipeline

Mon, 01 Jan 0001 00:00:00 +0000

You can use spin CLI to visualize a pipeline created from a pipeline template without actually instantiating one.

When you do this, you are creating JSON output that looks like regular pipeline JSON (plus the template reference and hydrated variables), but you’re not creating the actual pipeline in Spinnaker.

Using `spin pt plan`

spin pipeline-templates plan --file <path to pipeline config>

{
  "application": "my-spinnaker-app"
  "stages": [...] # Evaluated pipeline config based on template config values.
}

…where <path to pipeline config> points to the file you created when you instantiated a pipeline based on the template.

Set up Canary Analysis Support

Mon, 01 Jan 0001 00:00:00 +0000

Setting up automated canary analysis in Spinnaker consists of configuration for Kayenta which does canary analysis by querying metrics, storing the canary configuration templates, and storage for the canary reports in a storage location. Before you can use the canary analysis service, you must configure at least one metrics service, and at least one storage service. The most common setup is to have one metrics service configured (e.g. Stackdriver, Atlas, Prometheus, Datadog or New Relic) and one storage service (e.g. S3, GCS or Minio) configured.

Storage

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker requires a database for persisting your Application settings and configured Pipelines as well as execution history. A database is used for a few services (clouddriver, front50, orca). Because this data can be sensitive and can be costly to lose, we recommend you use a hosted storage solution you are confident in.

Supported databases

Spinnaker recommends MySQL/MariaDB or Postgresql. It’s recommended for most users to start with MariaDB/MySQL.

Services ship with mysql-connector-java by default. You can provide additional JDBC connectors on the classpath if desired. MySQL/MariaDB is reported to work all the way up to version 10 of MariaDB and the latest Aurora MySQL engines.

Clouddriver Account Management

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker 1.28 introduced an alpha API for loading, storing, updating, and otherwise managing Clouddriver account configurations from a database. Combined with a supported external secrets manager , account credentials can be provided by end users when setting up an account configuration.

The following table lists the Clouddriver account types that currently support the account management API. Note that the type discriminator is used as the value for the key @type in the JSON representation of an account definition.

External Account Configuration

Mon, 01 Jan 0001 00:00:00 +0000

This page describes Spinnaker’s external configuration feature. Using external configuration, you can manage account configuration (either complete account configuration, or only secrets such as account passwords) externally from Spinnaker.

External configuration uses the open-source Spring Cloud Config project, which includes a configuration server and client libraries to support centralized external configuration in a distributed system. The Config Server connects to a remote configuration repository and serves stored configuration properties to client applications.

Managed Delivery FAQ

Mon, 01 Jan 0001 00:00:00 +0000

What is happening?

Spinnaker is managing this resource. That means that the state of this resource is controlled using a declarative config submitted to Spinnaker.

Can I make changes in the UI to this resource?

Nope. Well, you can, but they will be almost immediately stomped to return to the declared state.

Who is the source of truth for that declared state?

Spinnaker is.

Then why do I have code checked into a repo?

To help you keep your resources in a known good state. You must publish these resource configs to Spinnaker every time they change in order for that change to be reflected in Spinnaker.

Configuration

Mon, 01 Jan 0001 00:00:00 +0000

There are a number of other things you can configure in your Spinnaker installation enumerated below. At any point in time, you can apply your configuration by deploying Spinnaker services:

kubectl kustomize -o spinnaker.yml
kubectl apply -f spinnaker.yml

Deploy to more cloud accounts

Documentation

You can add as many target accounts as you want. There is nothing preventing you from deploying to two Kubernetes clusters, one Google Compute Engine project, and an App Engine application all at once.

Setup FAQ

Mon, 01 Jan 0001 00:00:00 +0000

CAUTION

Halyard is deprecated and no longer supported. MANY FAQs here around halyard no longer work or are no longer relevant. See a Spinnaker Kustomize based installation for a current deployment of spinnaker. Halyard FAQs and information will be removed on an ongoing basis

I can’t load the Applications screen

After installing Spinnaker and navigating to the Applications screen, you may see one of following issues:

The following error message is displayed:

Error fetching applications. Check that your gate endpoint is accessible. Further information on troubleshooting this error is available here

The most common cause of this error is that your browser can’t communicate with your Gate endpoint. (This endpoint defaults to http://localhost:8084, but can be customized.)

Migrating from Operator/Halyard to Kustomize Deployment

Mon, 01 Jan 0001 00:00:00 +0000

Migrating to a Kustomize Deployment

Thank you to harness spinnaker team for the script and automation to enable migration to kustomize easily. This is a mirror from their documentation on migration off of operator and though operator specific in many aspects, this should work just as well for halyard deployments

Introduction

This document provides step-by-step instructions for migrating your Spinnaker installation from using the Armory Operator deployment method OR a halyard deployment to a native Kubernetes deployment using Kustomize. This approach gives you more direct control over your Spinnaker resources and removes the dependency on halyard

Component Sizing

Mon, 01 Jan 0001 00:00:00 +0000

CPU & Memory requests/limits

Container requests and limits for cpu and memory can be specified in the spinnaker-kustomize/base/*/deployments.yml files. Watch for OutOfMemory exceptions and monitor JVM Memory, CPU usage, and similar metrics to keep spinnaker up and running.

Limits and requests can be set per kubernetes documentation .

Updating JAVA_OPTS

All JVM-based services have the following JAVA_OPTS that can be set to adjust things like memory or additional flags. You can add these to the deployment ENV variables:

High Availability

Mon, 01 Jan 0001 00:00:00 +0000

Warning this is an advanced that most basic users never need to worry about

This page describes how you can configure a Spinnaker deployment to increase the availability/performance of specific services beyond simply horizontally scaling the services.

This is done by splitting the functionalities of a service into separate logical roles. The benefits of doing this is specific to the service that is being sharded. These deployment strategies are inspired by Netflix’s large scale experience .

Deprecated - Halyard

Mon, 01 Jan 0001 00:00:00 +0000

This documentation is deprecated as halyard is deprecated and no longer supported. This is left here for historical purposes

Halyard is a command-line administration tool that manages the lifecycle of your Spinnaker deployment, including writing & validating your deployment’s configuration, deploying each of Spinnaker’s microservices, and updating the deployment.

All production-capable deployments of Spinnaker require Halyard in order to install, configure, and update Spinnaker. Though it’s possible to install Spinnaker without Halyard, we don’t recommend it, and if you get stuck we’re just going to tell you to use Halyard.

Spinnaker Release 2026.2.3

Thu, 30 Jul 2026 22:07:13 +0000

Breaking Changes

Features

halyard: add kork-secrets-k8s dependency (#7788) (#7789) ( 394393c8 )
lambdaInvoke: Opt-In in resolving in Orca the Invoke payload artifact (#7867) (#7868) ( a50144fc )

Configuration

Fixes

build: Set group name on all root projects (#7834) (#7857) ( f7246ac3 )
cve: Fix an old CVE version of kayenta signalfx library (#7840) (#7844) ( 7021d0de )
cve: More cve lib fixes (#7841) (#7843) ( 055f90dc )
elastic: Bump elastic for CVE fixes (#7784) (#7785) ( 5fc25e30 )
gate: guard PermissionService.isAdmin(String) with fiatStatus.isEnabled() (#7783) (#7786) ( 4b1c4fc4 )
install: Use correct ARCH type for arm64 architecture during Rosco packer install (#7792) (#7793) ( ba642a61 )
libdiffs: order versions of differing component counts correctly (#7805) (#7815) ( f4f926da )
packer: pass through Boolean false and numeric 0 -var values (#7806) (#7812) ( e5d7ac42 )
parsing: Fixes the issue reported in https://github.com/spinnaker/spinnaker/pull/7686 and adds some null checks and blank handling (#7856) (#7860) ( b37b4ece )
sql: use inlined literal for compression_type to fix Postgres enum cast failure (#7778) (#7801) ( 277c26f0 )
yaml: Fix a few places that do not handle large yamls with new snakeyaml (#7748) (#7811) ( c866972b )

Other

Spinnaker Release 2026.1.2

Thu, 30 Jul 2026 21:07:38 +0000

Breaking Changes

Features

lambdaInvoke: Opt-In in resolving in Orca the Invoke payload artifact (#7867) (#7869) ( 7682b3a8 )

Configuration

Fixes

build: Defer publishing configuration until -bom subproject evaluation (#7727) (#7728) ( 185398d4 )
build: Set group name on all root projects (backport #7834) (#7858) ( 2304cbd5 )
build: Use default resolution for javaPlatform (#7732) (#7733) ( e7c74225 )
libdiffs: order versions of differing component counts correctly (#7805) (#7816) ( 228d8387 )
packer: pass through Boolean false and numeric 0 -var values (#7806) (#7813) ( 04d9836b )
parsing: Fixes the issue reported in https://github.com/spinnaker/spinnaker/pull/7686 and adds some null checks and blank handling (#7856) (#7861) ( 3ebb471d )

Other

Spinnaker Release 2026.0.4

Thu, 30 Jul 2026 20:07:48 +0000

Breaking Changes

Features

lambdaInvoke: Opt-In in resolving in Orca the Invoke payload artifact (#7867) (#7870) ( 0a578412 )

Configuration

Fixes

build: Defer publishing configuration until -bom subproject evaluation (#7727) (#7729) ( 7a02b4ca )
build: Set group name on all root projects (backport #7834) (#7859) ( ce15e35f )
build: Use default resolution for javaPlatform (#7732) (#7734) ( eb375e3b )
libdiffs: order versions of differing component counts correctly (#7805) (#7817) ( cd86b567 )
packer: pass through Boolean false and numeric 0 -var values (#7806) (#7814) ( d7b9b515 )
parsing: Fixes the run job output parsing issue and adds some null checks and blank handling (#7856) (#7862) ( ed3c9ee6 )

Other

Spinnaker Release 2026.2.2

Mon, 13 Jul 2026 04:07:46 +0000

Breaking Changes

Features

Configuration

Fixes

kayenta: Fix kayenta stage UI formatting (#7779) (#7780) ( fc9c8004 )

Other

cves: Upgrade various deps based on security scans (#7775) (#7776) ( 08fe0e57 )

Spinnaker Release 2026.2.1

Mon, 06 Jul 2026 20:07:42 +0000

Breaking Changes

Features

Configuration

Fixes

aws: bridge v1 credentials to v2 in AmazonCredentials.getV2CredentialsProvider() AmazonCredentials.getV2CredentialsProvider() returned DefaultCredentialsProvider which cannot discover AWS credentials in non-AWS environments (e.g. GKE pods). All Spinnaker accounts have a configured v1 AWSCredentialsProvider that already handles STS assume-role with token refresh, but the v2 path ignored it entirely. Bridge the v1 provider to v2 by adapting each resolved credential (supporting both session and basic credentials). This makes the v2 SDK path work everywhere the v1 path works, without requiring a separate v2 credential discovery chain. Also removes the now-unnecessary override from NetflixAssumeRoleAmazonCredentials since the base class handles it for all subclasses. (#7766) (#7767) ( 160c50ab )

Other

Spinnaker Release 2026.2.0

Wed, 01 Jul 2026 17:07:59 +0000

Deprecations and Removals

MySQL 8+ REQUIRED: With recent upgrades to the underlying SQL libraries, MySQL 5.7 is no longer supported and will fail. You must be on MySQL 8+ (or equivalent MariaDB) to use Spinnaker going forward.
Halyard: Halyard has been deprecated and will be removed from new publishing after this release. The current Halyard installation should continue to operate, but the code will be removed from the Spinnaker project core. Fixes can be backported as needed, but all users should migrate to an alternative installation method. Kustomize is the default documented and community-supported installation method.

Spinnaker Release 2025.4.4

Fri, 12 Jun 2026 18:06:56 +0000

Breaking Changes

Features

Configuration

Fixes

clouddriver/eureka: remove leading slashes from all the retrofit2 api interfaces (#7652) (#7661) ( 2ef5968c )
deck: Preserve execution selection when editing form fields (#7439) (#7698) ( 37108a77 )
echo: Fix Microsoft Teams webhook URL doubling in Retrofit2 migration (#7718) (#7721) ( 9e97bec6 )
echo: GitHub status conversion exception (#7701) (#7708) ( ffba1a55 )
tests: Add tests around retrofit incorrect call handling from previous PR (#7710) (#7724) ( bb91cca7 )
yaml: A few classes were not using safe constructors. Fix these (#7669) (backport to 2025.4.x) (#7691) ( e57c0db4 )

Other

change: Merge commit from fork (#7713) ( 2d75818b )

Spinnaker Release 2026.1.1

Fri, 12 Jun 2026 18:06:32 +0000

Breaking Changes

Features

Configuration

Fixes

echo: Fix Microsoft Teams webhook URL doubling in Retrofit2 migration (#7718) (#7719) ( a3e1f5e2 )
echo: GitHub status conversion exception (#7701) (#7706) ( 6f0250a4 )
tests: Add tests around retrofit incorrect call handling from previous PR (#7710) (#7722) ( 8d011e83 )

Other

change: Merge commit from fork (#7711) ( de5a7a05 )

Spinnaker Release 2026.0.3

Fri, 12 Jun 2026 18:06:29 +0000

Breaking Changes

Features

Configuration

Fixes

clouddriver/eureka: remove leading slashes from all the retrofit2 api interfaces (#7652) (#7660) ( 5900380b )
echo: Fix Microsoft Teams webhook URL doubling in Retrofit2 migration (#7718) (#7720) ( 5aec138d )
echo: GitHub status conversion exception (#7701) (#7707) ( 5c41f281 )
tests: Add tests around retrofit incorrect call handling from previous PR (#7710) (#7723) ( 7770adf6 )
yaml: A few classes were not using safe constructors. Fix these (#7669) (backport to 2026.0.x) (#7690) ( 4cbe1d5f )

Other

change: Merge commit from fork (#7712) ( bbc30c9b )

Spinnaker Release 2026.1.0

Sat, 09 May 2026 20:05:37 +0000

Security

There are a number of fixes in this release. As always upgrading post validation in a sandbox account is highly recommended. For example, the project moved from spring boot 3.1.2 to 3.1.12.

Breaking Changes

Halyard is fully deprecated at this point and no longer supported. Please migrate to spinnaker kustomize or a similar implementation going forward, as halyard will no longer be patched, updated, nor addressed for work
GHCR is now the default location for all images going forward. We will no longer be publishing to GAR, and in a few releases, all GAR access will be removed for docker images (debians are still published to GAR).

Certificate map support for GCP load balancers

Spinnaker supports caching and migration to certificate maps from ssl certificate configurations for load balancers.

Spinnaker Release 2025.3.3

Tue, 07 Apr 2026 19:04:23 +0000

Breaking Changes

Features

Configuration

Fixes

gate/web: return 200 instead of 500 for void orca endpoints (#7574) (#7576) ( d420f762 )
gitrepo: Fix git repo with some odd character combinations (#7564) (#7570) ( d5593b3f )

Other

Spinnaker Release 2026.0.2

Tue, 07 Apr 2026 19:04:16 +0000

Breaking Changes

Features

Configuration

Fixes

gate/web/test: remove stale comments in AdminControllerTest (#7584) (#7585) ( 87a79d27 )
gate/web: include additional exception message in AdminController.killZombie (#7575) (#7579) ( a0d688e0 )
gate/web: return 200 instead of 500 for void orca endpoints (#7574) (#7578) ( 4b41bdf5 )
gate: rename x509 SecurityFilterChain bean to prevent SAML override when both are enabled (backport #7539) (#7580) ( 60f45db4 )
gitrepo: Fix git repo with some odd character combinations (#7564) (#7568) ( 5468ff62 )
security: restore AnonymousConfig after Spring Boot 3 / Security 6 upgrade (#7538) (#7594) ( 3d031ab6 )

Other

Spinnaker Release 2025.4.3

Tue, 07 Apr 2026 19:04:12 +0000

Breaking Changes

Features

Configuration

Fixes

gate/web: return 200 instead of 500 for void orca endpoints (#7574) (#7577) ( 2cd80fb2 )
gate: rename x509 SecurityFilterChain bean to prevent SAML override when both are enabled (#7539) (#7581) ( c12a7d69 )
gitrepo: Fix git repo with some odd character combinations (#7564) (#7569) ( 369da6f0 )
saml: Fix wiring issue on saml. Add FULL end to end integration test using keycloak & htmlunitdriver (backport #7525) (#7607) ( 24959fc5 )
saml: Restore allowedAccounts (#7453) (#7608) ( 804c3fc4 )
security: restore AnonymousConfig after Spring Boot 3 / Security 6 upgrade (#7538) (#7593) ( 7adb4f7b )

Other

Spinnaker Release 2026.0.1

Fri, 20 Mar 2026 19:03:48 +0000

Breaking Changes

Features

Configuration

There’s an additional configuration that can be set on the gitrepo for controlling which hosts are accessible by a gitrepo. You can restrict now the gitrepo calls to ONLY internal servers vs. allowing multiple git servers. This can be done by adding an allowedhosts flag on the gitrepo accounts. NOTE: THis does NOT work in halyard so you’ll need to set these accounts via profiles if you’re still using halyard/operator.

Spinnaker Release 2025.4.2

Fri, 20 Mar 2026 18:03:48 +0000

Breaking Changes

Features

Configuration

Spinnaker Release 2025.3.2

Thu, 19 Mar 2026 20:03:29 +0000

Breaking Changes

Features

Configuration

Spinnaker Release 2026.0.0

Thu, 19 Feb 2026 05:02:12 +0000

Breaking Changes

Images

The spinnaker project will be moving docker images from Google’s artifact registry to GHCR going forward. This should save the project significantly on network and storage costs, while also allowing unlimited downloads. As such we’ve started publishing all images to the github packages pages . 2026.0.0 should be the last release consuming images from google artifact registry. Going forward, halyard and other images will start pulling from GHCR instead (incoming PRs shortly on this change). Please update any allowlists, rules, and mirrors to start using GHCR as a package repository. For more information, please join

Spinnaker Release 2025.2.4

Sat, 14 Feb 2026 20:02:49 +0000

Breaking Changes

Features

Configuration

Fixes

OAuth2: Remove quotes as it is causing URI issues while redirecting. (#7380) (#7381) ( 3558e844 )
build: actually publish compiled deck-kayenta code (#7389) (#7419) ( 9b1b4b0f )
deck: Attempt two of fixing deck publishing (backport #7406) (#7413) ( edb2ed1c )
gcp: Fix missing pagination token on accelerator lookups (#7420) (#7436) ( 1ab52111 )
kayentadeck: Fix publishing to NOT tag by latest. This prevents us from hitting an issue where backports fail to publish due to being older versions (#7456) (#7459) ( b1559cfa )
npm: Fix npm publishing (#7398) (#7412) ( a649739b )
orca-applications: Retrofit calls on Front50 projects tasks (#7272) (#7393) ( 9741b74e )
publishing: Fix deck kayenta had duplicate package block (#7444) (#7447) ( c53f05bd )
publishing: Fix image publishing for deck due to NPM trusted publishing change (#7422) (#7425) ( 9bd2194b )
publishing: NPM Tag update ( b2634575 )
validation: Fixes some url validation handling on underscores (backport #7428) (#7442) ( 1db6abf1 )

Other

build: Add id permissions to release for deck NPM publishing (#7448) (#7451) ( fbcbd0e4 )
build: migrate to trusted npm publishing (backport #7379) (#7416) ( 0549fd93 )

Spinnaker Release 2025.3.1

Sat, 14 Feb 2026 18:02:36 +0000

Breaking Changes

Features

Configuration

Fixes

OAuth2: Remove quotes as it is causing URI issues while redirecting. (#7380) (#7382) ( d03b0ad5 )
build: actually publish compiled deck-kayenta code (#7389) (#7418) ( 8ea3baac )
deck: Attempt two of fixing deck publishing (backport #7406) (#7411) ( 1411a9cd )
gcp: Fix missing pagination token on accelerator lookups (#7420) (#7435) ( a34f9f93 )
kayentadeck: Fix publishing to NOT tag by latest. This prevents us from hitting an issue where backports fail to publish due to being older versions (#7456) (#7458) ( 2ed5a0eb )
npm: Fix npm publishing (#7398) (#7409) ( 61bcf573 )
publishing: Fix deck kayenta had duplicate package block (#7444) (#7446) ( fa857f76 )
publishing: Fix image publishing for deck due to NPM trusted publishing change (#7422) (#7424) ( f651b23a )
publishing: Tags cant be semver so prefix with release (#7460) (#7462) ( c973386a )
validation: Fixes some url validation handling on underscores (backport #7428) (#7441) ( 9b3fe2b0 )

Other

build: Add id permissions to release for deck NPM publishing (#7448) (#7450) ( afc84eaf )
build: migrate to trusted npm publishing (#7379) (#7415) ( 82aef6bb )
roles: make fiat full role sync synchronized across fiat instan…" (#7348) (#7394) ( 61df749e )

Spinnaker Release 2025.4.1

Tue, 03 Feb 2026 00:02:53 +0000

Breaking Changes

Features

Configuration

Fixes

OAuth2: Remove quotes as it is causing URI issues while redirecting. (#7380) (#7383) ( 826e6adf )
gcp: Fix missing pagination token on accelerator lookups (#7420) (#7434) ( fc30c3dc )
orca/web: properly deserialize webhook status code (#7367) (#7368) ( 6bb03290 )
validation: Fixes some url validation handling on underscores (backport #7428) (#7440) ( 31d40976 )

Other

deck: actually publish compiled deck-kayenta code (#7389) (#7417) ( 43c99069 )
build: Attempt two of fixing deck publishing (backport #7406) (#7410) ( 27f0bf35 )
build: Fix deck kayenta had duplicate package block (#7444) (#7445) ( aa57ea00 )
build: Fix image publishing for deck due to NPM trusted publishing change (#7422) (#7423) ( f3b93fbc )
build: Fix npm publishing (#7398) (#7408) ( efa2f298 )
build: migrate to trusted npm publishing (#7379) (#7414) ( 6ea43243 )
orca/web: reproduce anonymous pipeline trigger user (#7369) (#7374) ( 57f98fe3 )

Spinnaker Release 2025.4.0

Mon, 01 Dec 2025 23:12:33 +0000

Breaking Changes

Spring Boot 3.0.13 Upgrade

As part of the upgrade to Spring Boot 3.0.13, actuator metrics export configuration properties have changed structure.

Actuator Metrics Export Property Changes

The metrics export properties have moved from the old schema to the new format:

Old Property Prefix	New Property Prefix
`management.metrics.export.<product>`	`management.<product>.metrics.export`

Example

Prometheus configuration keys have changed from:

management.metrics.export.prometheus.*

to

management.prometheus.metrics.export.*

Session data cleanup

Spring Boot 3.0 considers session data cached by Spring Boot 2.7 invalid. Therefore, users with cached sessions will be unable to log in until the invalid information is removed from the cache. Open browser windows to Spinnaker are unresponsive after the deployment until they’re reloaded. Executing:

Spinnaker Release 2025.3.0

Sat, 08 Nov 2025 00:11:07 +0000

Breaking Changes

S3ArtifactValidator’s validate method signature has changed when clouddriver-artifacts was upgraded to AWS SDK v2. Any custom implementations of this interface need to be updated accordingly. AWS SDK v2 upgrade PR: https://github.com/spinnaker/spinnaker/pull/7301

Features

Security settings on http based artifacts.

Any http or similar artifacts can now set some limits on accessible accounts. It’s recommended to configure an allow list to restrict calls to allowed known domains. There’s a whitelist of domains that can be set. Example of the configuration:

Spinnaker Release 2025.1.6

Fri, 07 Nov 2025 17:11:38 +0000

Breaking Changes

Features

Configuration

Fixes

config: Defaults are not being set when only a few fields are set (#7285) (#7287) ( 52f54124 )
echo: Fix rest event config to work with splunk style URLs or those without a trailing slash on the URL (#7330) (#7332) ( ac327cb6 )
gate-web: Controller fix for RoleController & EcsCloudMetricController after retrofit updates (#7303) (#7305) ( 653442e8 )
images: Fix a few more places querying for images that had null parameters causing failures due to retrofit changes (#7321) (#7329) ( 69792c33 )
orca-clouddriver: Fix findImages oortService call query map (#7278) (#7318) ( e45b2043 )
orca/redis: actually run the tests (#7292) (#7294) ( 1aa81a49 )

Other

change: Merge commit from fork (#7280) ( 54259cac )

Spinnaker Release 2025.2.3

Fri, 07 Nov 2025 17:11:32 +0000

Breaking Changes

Features

Configuration

Fixes

clouddriver/cloudformation: fix an API failure caused by encoded colon char post retrofit2 upgrade (#7262) (#7275) ( be71bba3 )
config: Defaults are not being set when only a few fields are set (#7285) (#7286) ( dd59e7f2 )
echo: Fix rest event config to work with splunk style URLs or those without a trailing slash on the URL (#7330) (#7331) ( c6907c53 )
gate-web: Controller fix for RoleController & EcsCloudMetricController after retrofit updates (#7303) (#7306) ( 19d27f1c )
images: Fix a few more places querying for images that had null parameters causing failures due to retrofit changes (#7321) (#7328) ( 3750eca6 )
orca-clouddriver: Fix findImages oortService call query map (#7278) (#7317) ( cf4a7428 )
orca/clouddriver/retrofit: fix wildcard in the retrofit method parameter (#7264) (#7267) ( b91f789a )
orca/redis: actually run the tests (#7292) (#7295) ( f9cf87cd )

Other

change: Merge commit from fork (#7279) ( dbabd821 )
orca: add a test to verify clouddriver GET api to get CloudFormationStack (#7248) (#7276) ( 74192b53 )

Spinnaker Release 2025.1.5

Mon, 13 Oct 2025 11:10:50 +0000

Breaking Changes

Features

Configuration

Fixes

clouddriver/cloudformation: fix an API failure caused by encoded colon char post retrofit2 upgrade (#7262) (#7274) ( 8f783f28 )
orca/clouddriver/retrofit: fix wildcard in the retrofit method parameter (#7264) (#7266) ( 4223404b )

Other

orca: add a test to verify clouddriver GET api to get CloudFormationStack (#7248) (#7277) ( 8172b817 )

Spinnaker Release 2025.2.2

Wed, 24 Sep 2025 20:09:33 +0000

Breaking Changes

Features

Configuration

Fixes

oauth2: move tokenResponseClient bean to static inner config to avoid circular dependency (#7254) (#7255) ( 02284135 )

Other

Spinnaker Release 2025.2.1

Mon, 22 Sep 2025 19:09:25 +0000

Breaking Changes

Features

Configuration

Fixes

OAuth2, NPE: Map.copyOf is strict about nulls so use Collections.unmodifiableMap instead (#7246) (#7252) ( 63dcf960 )

Other

Spinnaker Release 2025.2.0

Thu, 11 Sep 2025 19:09:01 +0000

Changelog

Breaking Changes

Clouddriver

https://github.com/spinnaker/spinnaker/pull/7240 changes constructors in AmazonCredentials / AssumeRoleAmazonCredentials / NetflixAmazonCredentials / NetflixAssumeRoleAmazonCredentials. Plugins or custom code may need corresponding changes (e.g. pass null for AwsConfigurationProperties) to continue to build.

Gate

Spring Security 5 Oauth2 Migration

https://github.com/spinnaker/spinnaker/pull/7052 removes deprecated OAuth2 annotations, and uses Spring Security 5’s DSL. Various steps are required for this upgrade. The properties for configuring OAuth2 in Gate have changed:

OAuth2 Configuration Property Mapping

security.authn.oauth2.enabled
  -> spring.security.oauth2.client (auto-configured by Spring Security)

security.authn.oauth2.provider
  -> spring.security.oauth2.client.registration.<providerId> (if provider is not specified in the old configuration, it should be set to 'other' in the new configuration)

security.authn.oauth2.client.clientId
  -> spring.security.oauth2.client.registration.<providerId>.client-id

security.authn.oauth2.client.clientSecret
  -> spring.security.oauth2.client.registration.<providerId>.client-secret

security.authn.oauth2.client.scope
  -> spring.security.oauth2.client.registration.<providerId>.scope

security.authn.oauth2.client.clientAuthenticationScheme
  -> spring.security.oauth2.client.registration.<providerId>.clientAuthenticationScheme

security.authn.oauth2.client.preEstablishedRedirectUri
  -> spring.security.oauth2.client.registration.<providerId>.redirect-uri (url should be in this format https://<your-domain>/login/oauth2/code/<providerid>)

security.authn.oauth2.client.userAuthorizationUri
  -> spring.security.oauth2.client.provider.<providerId>.authorization-uri

security.authn.oauth2.client.accessTokenUri
  -> spring.security.oauth2.client.provider.<providerId>.token-uri

security.authn.oauth2.resource.userInfoUri
  -> spring.security.oauth2.client.provider.<providerId>.user-info-uri

security.authn.oauth2.userInfoMapping
  -> spring.security.oauth2.client.registration.userInfoMapping

security.authn.oauth2.userInfoRequirements
  -> spring.security.oauth2.client.registration.userInfoRequirements

Below are some example configurations built based on above mapping.

Spinnaker Release 2025.1.4

Wed, 03 Sep 2025 19:09:12 +0000

Breaking Changes

Features

Configuration

Fixes

gcp: More NPE handling on some input (#7236) (#7237) ( 347cfb20 )

Other

Spinnaker Release 2025.1.3

Tue, 02 Sep 2025 17:09:52 +0000

Breaking Changes

Features

Configuration

Fixes

gate/web: add Retrofit2SyncCall.execute to SubnetController.allByCloudProvider (#7219) (#7221) ( 9b5dcd7b )
gcp: Fix a number of potential NPEs around deploy handling for google builds. Tied to groovy to java migration (#7227) (#7233) ( 4ea0d508 )
halyard/retrofit2: fix DaemonService’s convertor factory (#7230) (#7232) ( 66ade3f8 )
orca/retrofit2: fix orca bakeservice api (#7224) (#7225) ( e0a64b30 )

Other

Spinnaker Release 2025.0.8

Fri, 22 Aug 2025 17:08:38 +0000

Breaking Changes

Features

Configuration

Fixes

gate/web: add Retrofit2SyncCall.execute to SubnetController.allByCloudProvider (#7219) (#7220) ( 27179ec2 )

Other

Spinnaker Release 2025.1.2

Thu, 21 Aug 2025 20:08:00 +0000

Breaking Changes

Features

Configuration

Fixes

clouddriver/aws: align CredentialsParser types in AmazonCredentialsInitializer (#7207) (#7208) ( 3c45b4c9 )
echo/rest: make it possible to send events to URLs with no trailing slash (#7212) (#7215) ( 824acc94 )
google: Add retry and status polling logic (#7191) (#7217) ( b1243f81 )
halyard/retrofit2: fix daemon service getTask API definition (#7206) (#7209) ( a75b383c )

Other

Spinnaker Release 2025.0.7

Thu, 21 Aug 2025 18:08:04 +0000

Breaking Changes

Features

Configuration

Fixes

echo/rest: make it possible to send events to URLs with no trailing slash (#7212) (#7214) ( dd7714d9 )
echo/retrofit2: fix the handling of responses from APIs of GoogleChat and Slack (#7175) (#7181) ( 1ff8e285 )
keel: add executor pool for asynchronous requests (#7190) (#7194) ( 057df0d4 )
orca/retrofit: replace RetrofitError with SpinnakerServerException in orca.yml to add automatic retries to API calls that might fail transiently. (#7180) (#7182) ( 41d8bd3a )

Other

Spinnaker Release 2025.1.1

Tue, 19 Aug 2025 21:08:45 +0000

Breaking Changes

Features

Configuration

Fixes

orca/clouddriver: correct parameter order for requestOperations to avoid invalid cloudProvider errors (#7201) (#7204) ( 7f6e3e2f )

Other

Spinnaker Release 2025.1.0

Tue, 19 Aug 2025 18:08:49 +0000

Changelog

Breaking Changes

https://github.com/spinnaker/spinnaker/pull/7173 removed retrofit1 from Spinnaker. Specifically, spinnaker-dependencies no longer refers to com.squareup.retrofit:retrofit:1.9.0 (and some other related jars as well). Plugins or custom code that depend on this need to add their own dependencies or upgrade to retrofit2.

Helm OCI Registry Chart Support

Docker registry provider now supports adding OCI-based registries hosting Helm repositories. This feature allows users to download and bake Helm charts hosted in OCI-compliant registries (such as Docker Hub).

Spinnaker Release 1.36.3

Fri, 15 Aug 2025 18:14:37 +0000

Clouddriver 5.90.5

The primary change here is a configuration (defaulted to true) that instead of immediately moving on after a deploy operation instead polls for task completion of the operation. There is a case where Google will not complete the operation or even fail the operation and instead of detecting this, spinnaker would go to the next task and fail. See issue 7170 for more information.

This WILL add some extra time on deployments and the legacy behavior can be disabled via a configuration property documented in the enableAsyncOperationWait PR.

Spinnaker Release 2025.0.6

Thu, 24 Jul 2025 22:07:53 +0000

Breaking Changes

Features

retrofit2: Add CallAdapter for legacy Retrofit signatures (#7088) (#7155) ( eced8bbe )

Configuration

Fixes

googlechat: fix googlechat encoding issue (#7165) (#7166) ( e0ca3882 )
retrofit2: fix a broken scenario related to LegacySignatureCallAdapter (backport #7131) (#7135) ( 4fb42281 )
retrofit2: remove leading slashes from all the retrofit2 api interfaces (backport #7159) (#7160) ( 450f01e1 )
retrofit: fix retrofit1 client definition in kork (#7130) ( ae505cdc )

Other

front50/retrofit2: upgrade the lone EchoService interface to retrofit2 in front50 (#7151) (#7153) ( fb781906 )
gha: run clouddriver integration tests when kork or fiat change (backport #7156) (#7158) ( 14c9e06e )
gha: run clouddriver k8s integration tests when the workflow is modified (#7157) ( b5de0d40 )

Spinnaker Release 2025.0.5

Tue, 15 Jul 2025 19:07:50 +0000

Breaking Changes

Features

Configuration

Fixes

build: Enable publishing for Gradle plugins (#7122) (#7128) ( 5e58dc70 )
publishing: Write all versions to Maven metadata (#7126) (#7127) ( c1b4d73d )
retrofit2: fix query param encoding logic to accommodate repeating query params (#7133) (#7134) ( 7252a084 )

Other

build: Migrate from OSSRH to Central Portal (#7114) (#7123) ( 745c1e81 )
clouddriver/kubernetes: test against a 1.30.13 k8s cluster (#7139) (#7141) ( abe2528f )
clouddriver/kubernetes: upgrade kind to 0.29.0 (#7138) (#7142) ( 8c463a59 )

Spinnaker Release 2025.0.4

Mon, 16 Jun 2025 21:06:26 +0000

Breaking Changes

Features

Configuration

Fixes

docker: fix missing slash issue of docker registry client’s base url (backport #7110) (#7111) ( 9151b959 )
igor-web: fix Jenkins job’s build response handling issue (#7105) (#7107) ( f65eb2c4 )
test: move test file to the right location (#7102) (#7103) ( a991d2d2 )

Other

Spinnaker Release 2025.0.3

Sat, 24 May 2025 14:05:08 +0000

Breaking Changes

Features

Configuration

Fixes

build: Fix BoM generation against release tags (#7081) (#7083) ( 0a75021d )
build: Limit versions.yml to three releases, and collapse patch versions (#7086) (#7087) ( 168f447a )
build: Publish debs on release (#7091) (#7092) ( 75c5e544 )
build: Update top-level versions.yml metadata if release is newest (#7080) (#7082) ( fe9ebe5e )

Other

Spinnaker Release 1.36.2

Thu, 22 May 2025 18:13:27 +0000

Clouddriver 5.90.2

Fixes

aws: Launch template version of ASG default to when not defined (#6373) ( 3984ca5a )
clouddriver-google: Fix logic when Instance Types are available only in selected Zones/Regions - manual backport ( 482dda72 )
clouddriver-google: Fix logic when Instance Types are available only in selected Zones/Regions - manual backport ( 482dda72 )
clouddriver-google: Fix logic when Instance Types are available only in selected Zones/Regions ( 482dda72 )
ecs: evaluate targetgroup healthcheck in instance healthcheck (#6307) ( c8c9d4c8 )
ecs: include healthcheck status from targetgroups in instance healthcheck ( c8c9d4c8 )
ecs: check null for loadBalancer attribute ( c8c9d4c8 )
ecs: evaluate TargetHealth check if container deployed does have target groups associated ( c8c9d4c8 )

Other

dependencies: Autobump fiatVersion ( 1730ad7c )
dependencies: Autobump korkVersion ( 0c7cff1d )
ecs: add tests for default behavior and targetgroup healthchecks ( c8c9d4c8 )
ecs: improve testing and use targetHealth to determine status only if containerHealthcheck is UNKNOWN ( c8c9d4c8 )

Deck 3.19.2

Fixes

core: Always use clusters parameter for ECS server group URLs (#10171) ( 127fa906 )
core: Always use clusters parameter for ECS server group URLs ( 127fa906 )
core: Extend server group URL fix to handle both ECS and AWS providers ( 127fa906 )
gcp: fixing existing test + adding one test and updating credentials.json (#10166) ( 1b8f60af )

Echo 2.43.3

Fixes

notifications: Prevent duplicate notifications for Manual Judgment stages (#1506) ( 0dbf85c0 )

Other

dependencies: Autobump fiatVersion ( babe7819 )
dependencies: Autobump korkVersion ( 4fefb47d )

Fiat 1.51.2

Other

dependencies: Autobump korkVersion ( 6c46d685 )

Front50 2.37.2

Other

dependencies: Autobump fiatVersion ( 3325d3cd )
dependencies: Autobump korkVersion ( 6b38756d )

Gate 6.64.2

Fixes

saml: With the upgrade to spring saml off of the DSL signing saml requests were broken. This restores that capability (#1898) ( e551157a )
swagger: ensure byteArrayHttpMessageConverter is the first converter to render swagger UI (#1865) ( 251d2505 )
swagger: ensure byteArrayHttpMessageConverter is the first converter to render swagger UI ( 251d2505 )

Other

dependencies: Autobump fiatVersion ( 938d70eb )
dependencies: Autobump korkVersion ( ff320db1 )
swagger: add test for swagger openapi migration ( 251d2505 )
swagger: refactor fix and rename swagger test ( 251d2505 )

Igor 4.18.2

Other

dependencies: Autobump fiatVersion ( c23e997b )
dependencies: Autobump korkVersion ( 992af5a9 )

Kayenta 2.42.2

Other

dependencies: Autobump orcaVersion ( 6b6a9dde )

Orca 8.57.2

Other

dependencies: Autobump fiatVersion ( 5f3b9f44 )
dependencies: Autobump korkVersion ( 321513c2 )

Rosco 1.22.2

Fixes

install: Fixed packer version check for packer installation (#1121) ( 469879dc )

Other

dependencies: Autobump korkVersion ( dbaeacd4 )

Spinnaker Release 2025.0.2

Sat, 17 May 2025 07:05:53 +0000

Breaking Changes

Features

Configuration

Fixes

web: fix HelmConverterFactory for deserialization error (#7077) (#7079) ( 4cf4d420 )

Other

Spinnaker Release 2025.0.1

Mon, 12 May 2025 20:05:16 +0000

Breaking Changes

Features

Configuration

Fixes

build: Fix previous-version changelog arg, filter changelog commits (#7045) (#7046) ( 03a3c471 )
changelog: Use proper seconds date format (#7047) (#7048) ( 29bca907 )
config: fix the issue of halyard failing to add docker registry account (#7066) (#7068) ( 0d5a0591 )
docker: fix the issue of fetching docker images (#7073) (#7074) ( 4f9ba539 )
rest: fix the retrofit2 error messages coming in the test logs of RestEventListenerTest (#7055) (#7058) ( 081cd201 )
retrofit2: fix the issue of retrofit2 being unable to convert the Event object to RequestBody. (#7060) (#7067) ( 972e36bc )

Other

Spinnaker Release 1.37.11

Mon, 12 May 2025 19:46:56 +0000

Clouddriver 5.91.7

Fixes

docker: fix the issue of fetching docker images ( e8f7a1aa )
docker: fix the issue of fetching docker images due to java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1 ( e8f7a1aa )

Other

docker: add a test to demonstrate the issue of fetching docker images due to java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1 ( e8f7a1aa )

Igor 4.19.3

Fixes

jenkins: fix the issue of Retrofit2EncodeCorrectionInterceptor getting added to Jenkins retrofit1 client ( 840fdb61 )
jenkins: fix the issue of Retrofit2EncodeCorrectionInterceptor getting added to retrofit1 client of JenkinsClient. ( 840fdb61 )
jenkins: address review comments ( 840fdb61 )

Other

jenkins: add a test to demonstrate the issue of Retrofit2EncodeCorrectionInterceptor getting added to retrofit1 client of JenkinsClient ( 840fdb61 )
jenkins: Convert JenkinsClientSpec groovy test to java ( 840fdb61 )

Spinnaker Release 2025.0.0

Sat, 19 Apr 2025 02:04:00 +0000

Changelog

Version 2025.0.0 is the first version of Spinnaker released from the monorepo . It’s equivalent to version 1.38.0 which was released using the individual repos.

Spinnaker Release 1.38.0

Fri, 18 Apr 2025 20:26:42 +0000

Changelog

echo

Version 1.31.0 of Spinnaker introduced a feature to filter pipelines from front50 , that was disabled by default. Version 1.35.0 enabled it by default , but we’ve had enough trouble with it, that https://github.com/spinnaker/echo/pull/1503 disables it by default again.

retrofit2 upgrade

All retrofit clients are upgraded to retrofit2 and any references to retrofit1 dependencies are removed in the following services.

Igor - https://github.com/spinnaker/igor/pull/1313

Clouddriver 5.95.0

Fixes

clouddriver-google: Fix logic when Instance Types are available only in selected Zones/Regions ( 6a65adfd )
core/test: add a Retrofit2EncodeCorrectionInterceptor bean ( 70b14c1a )
docker: resolve the issue of Unrecognized field "child" ( 7c4514af )
docker: resolve the issue of Failed to parse ResponseBody : Unrecognized field "child" when google cloud artifact registry responds with additional fields upon invoking tags list api ( 7c4514af )
docker: resolve the issue of double encoding while making the next call to ECR’s tags list ( 06c98c00 )
docker: resolve the issue of double encoding contained in the ECR’s next link header causing the Retrofit2 client to fail due to error code 405 and Message: Method Not Allowed. ( 06c98c00 )
docker: fix retrofit2 docker client which is replacing ? with %3F causing api failure ( 02101899 )
docker: fix the issue of retrofit2 replacing ? with %3F causing api failure with 400 ( 02101899 )
docker: address review comments on the fix to the issue of retrofit2 replacing ? with %3F causing api failure with 400 ( 02101899 )
docker/test: add a Retrofit2EncodeCorrectionInterceptor bean ( 70b14c1a )

Other

cats-sql: actually execute groovy tests ( 23155e5b )
dependencies: Autobump fiatVersion ( 5e0ce2ab )
dependencies: Autobump korkVersion ( 4d80be21 )
dependencies: Autobump fiatVersion ( 06fbc3d5 )
dependencies: Autobump korkVersion ( 3a2356f0 )
dependencies: Autobump fiatVersion ( 5a1709a4 )
dependencies: Autobump korkVersion ( 70b14c1a )
dependencies: Autobump korkVersion ( 70b14c1a )
docker: add a test to demonstrate the issue of Failed to parse ResponseBody : Unrecognized field "child" ( 7c4514af )
docker: add test to demonstrate the issue of double encoding of query parameter when the next link from a docker registry like ECR responds with an encoded url. ( 06c98c00 )
docker: add two test classes, one to demonstrate how real docker registry apis can be accessed using retrofit2 client and another to demonstrate the issue of retrofit2 replacing ? with %3F causing api failure with 400 ( 02101899 )

Deck 3.21.0

Fixes

gcp: fixing existing test + adding one test and updating credentials.json ( 2740ed53 )
pipelineStage: Rendering with a warning with the pipelineParameters are defined as a SpeL expression ( 294e0ed1 )

Echo 2.47.2

Fixes

notifications: fix MicrosoftTeamsConfig which has unused retrofit1 parameters ( 41b18321 )
notifications: add Retrofit2SyncCall.execute to BearychatService in BearychatNotificationService ( 8a2b94af )
notifications: add Retrofit2SyncCall.execute to BearychatService in BearychatNotificationService ( 8a2b94af )
pipelinetriggers: turn off pipeline filtering by default (#1503) ( 38c2df6d )
rest: add Retrofit2SyncCall.execute to RestService in RestEventService ( d3c1833b )
rest: add Retrofit2SyncCall.execute to RestService in RestEventService ( d3c1833b )
retrofit: address remnants of retrofit1 like TypedInput, TypedByteArray etc ( 5132fa85 )
retrofit: address remnants of retrofit1 like TypedInput, TypedByteArray etc ( 5132fa85 )
retrofit2: fix google cloud build notification agent for missing Retrofit2SyncCall.execute call (#1500) ( 7de326a1 )
retrofit2: fix the issue of missing Retrofit2SyncCall.execute call in GoogleCloudBuildNotificationAgent ( 7de326a1 )
retrofit2: fix A @path parameter must not come after a @Query error ( f170364c )
retrofit2: fix A @Path parameter must not come after a @Query error ( f170364c )
retrofit2: fix baseUrl must end in / error ( 19e2f34d )
retrofit2: fix the following error by adding trailing / in the baseUrl and removing leading / in the end point: ( 19e2f34d )
retrofit2: fix RestService by replacing POST mapping from / to . and add a test class to demonstrate the behaviour. ( 19e2f34d )
retrofit2/test: deal with the introduction of Retrofit2EncodeCorrectionInterceptor ( 3b759058 )

Other

core/test: only spin up a wiremock server once in IgorServiceTest ( 5132fa85 )
dependencies: Autobump fiatVersion ( 4c0e2959 )
dependencies: Autobump korkVersion ( c4fac745 )
dependencies: Autobump fiatVersion ( b2fe9a12 )
dependencies: Autobump korkVersion ( 3fb1fd6a )
dependencies: Autobump fiatVersion ( db1889af )
dependencies: Autobump korkVersion ( 3b759058 )
dependencies: Autobump korkVersion ( 3b759058 )
notifications: add a test to demonstrate the missing Retrofit2SyncCall.execute calls in BearychatNotificationService ( 8a2b94af )
rest: add a test to demonstrate that RestEventService.sendEvent is failing to make the RestService.recordEvent api call ( d3c1833b )
retrofit: add a test to demonstrate the issue of passing a TypedInput while using retrofit2 client ( 5132fa85 )
retrofit2: add a test to demonstrate the issue of missing Retrofit2SyncCall.execute call in GoogleCloudBuildNotificationAgent ( 7de326a1 )
retrofit2: add a test to demonstrate the following error: ( f170364c )
retrofit2: add a test to demonstrate the error: java.lang.IllegalArgumentException: baseUrl must end in /. ( 19e2f34d )

Fiat 1.57.0

Fixes

github: fix the error where if the baseUrl of the Github client has multiple slashes and the end point start with a slash, the resultant api url leaves that part the base url coming after first slash. ( a7f7f9de )
retrofit2: fix multiple slash issue in baseUrl of retrofit2 client ( a7f7f9de )

Other

api: refactor retrofit2 client configuration for FiatService to fix any issues that may occur if the base url has multiple slashes ( a7f7f9de )
dependencies: Autobump korkVersion ( 1c7fb38c )
dependencies: Autobump korkVersion ( e6fa9be1 )
dependencies: Autobump korkVersion ( 0b9e5f6f )
github: add a test to demonstrate an error scenario where if the baseUrl of the Github client has multiple slashes and the end point start with a slash ( a7f7f9de )
web: refactor retrofit2 client configuration for IgorApi, ClouddriverApi and Front50Api to fix any issues that may occur if the base url has multiple slashes ( a7f7f9de )

Front50 2.41.0

Other

dependencies: Autobump fiatVersion ( ceda49e0 )
dependencies: Autobump korkVersion ( 849a0ce3 )
dependencies: Autobump fiatVersion ( c4c047b5 )
dependencies: Autobump korkVersion ( e8909c70 )
dependencies: Autobump fiatVersion ( 6dc06b63 )
dependencies: Autobump korkVersion ( 84137d73 )

Gate 6.69.0

Fixes

retrofit2: fix retrofit2 issues ( bdf8922b )
retrofit2: fix non-generics QueryMap which causes the following error: ( bdf8922b )
retrofit2: fix A @Path parameter must not come after a @Query error ( bdf8922b )
retrofit2/test: deal with the introduction of Retrofit2EncodeCorrectionInterceptor ( c18a17c1 )
web: fix the mismatch in return types of EchoService.postEvent api stub and the actual api from echo ( ed770271 )
web: fix the mismatch in return types of EchoService.postEvent api stub and the actual api from echo. ( ed770271 )
web: fix the mismatches in the return types of APIs in gate and orca ( 15465c96 )
web: fix the mismatches in the return types of apis in gate and orca for delete, resume, cancel and pause operations of a pipeline. ( 15465c96 )
web: add Retrofit2SyncCall.execute to ClouddriverService in CredentialsController ( 5b500d3c )
web: add Retrofit2SyncCall.execute to ClouddriverService in CredentialsController ( 5b500d3c )
web: add Retrofit2SyncCall.execute to BakeService ( d3dc67d6 )
web: add Retrofit2SyncCall.execute to BakeService ( d3dc67d6 )
web: make type of additionalFilters in ImageController.findImages ( 875a8b15 )
web: make type of additionalFilters in ImageController.findImages ( 875a8b15 )

Other

Add test cases for OAuth feature validation ( a33b053e )
OAuth2: groovy to java conversion for OAuth module ( 381f554c )
OAuth2: groovy to java conversion for OAuth module ( 381f554c )
dependencies: Autobump fiatVersion ( 1af7f70a )
dependencies: Autobump korkVersion ( 8f5cffb6 )
dependencies: Autobump fiatVersion ( d04b861c )
dependencies: Autobump korkVersion ( efd741a5 )
dependencies: Autobump fiatVersion ( dd8ea4b3 )
dependencies: Autobump korkVersion ( c18a17c1 )
dependencies: Autobump korkVersion ( c18a17c1 )
retrofit2: add test to demonstrate the following error when QueryMap is used without generics: ( bdf8922b )
web: add a test to demonstrate the mismatch in return types of EchoService.postEvent api stub and the actual api from echo. ( ed770271 )
web: add a test to demonstrate the mismatch in api response types of gate and orca when delete pipeline execution api is invoked ( 15465c96 )
web: add a test to demonstrate the retrofit error that occurs when /credentials/type/{accountType} is invoked ( 5b500d3c )
web: use constructor injection in BakeService ( d3dc67d6 )
web: demonstrate behavior of BakeService ( d3dc67d6 )
web: demonstrate behavior of ImageController.findImages ( 875a8b15 )
web/test: mock DefaultProviderLookupService in PipelineServiceTest ( 15465c96 )
web/test: remove request id header from PipelineServiceTest ( 15465c96 )
web/test: add X-SPINNAKER-USER and X-SPINNAKER-ACCOUNTS headers ( 15465c96 )

Igor 4.22.0

Fixes

monitor-travis/test: keep up with new Retrofit2EncodeCorrectionInterceptor argument ( 5921e5fc )
web/test: keep up with new Retrofit2EncodeCorrectionInterceptor argument ( 5921e5fc )

Other

dependencies: Autobump fiatVersion ( 627ec479 )
dependencies: Autobump korkVersion ( f4f2da07 )
dependencies: Autobump fiatVersion ( 44c1bd8b )
dependencies: Autobump korkVersion ( 0c90099a )
dependencies: Autobump fiatVersion ( 22985a3d )
dependencies: Autobump korkVersion ( 5921e5fc )
dependencies: Autobump korkVersion ( 5921e5fc )
retrofit2: upgrade code to use retrofit2 ( 769f1751 )
retrofit2: upgrade igor-core package to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-monitor-artifactory to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-monitor-plugins to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-monitor-travis to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-web jenkins code to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-web bitbucket code to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-web github code to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-web gitlab code to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-web stash code to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-web wercker code to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-web concourse code to retrofit2 ( 769f1751 )
retrofit2: upgrade igor-web helm code to retrofit2 ( 769f1751 )
retrofit2: upgrade remaining misc files in igor-web to retrofit2 ( 769f1751 )
retrofit2: add missing Retrofit2SyncCall.execute() calls ( 769f1751 )
retrofit2: remove leading slashes in endpoints + add utility class to prevent ‘baseUrl must end in /’ error ( 769f1751 )
retrofit2: add tests for retry behavior in GitlabCiService ( 769f1751 )
retrofit2: fix connection refused in RetrofitUtilsTest ( 769f1751 )
retrofit2: fix formatting ( 769f1751 )
retrofit2: remove JenkinsOkHttpClientProvider and DefaultJenkinsOkHttpClientProvider ( 769f1751 )

Kayenta 2.46.0

Other

dependencies: Autobump orcaVersion ( a69573be )
dependencies: Autobump orcaVersion ( 4c545b5f )

Orca 8.64.0

Fixes

clouddriver/test: keep up with new Retrofit2EncodeCorrectionInterceptor argument ( d04c5186 )
retrofit1: exclude Retrofit2EncodeCorrectionInterceptor from the retrofit1 clients ( 2fdb327a )
retrofit1: exclude Retrofit2EncodeCorrectionInterceptor from the retrofit1 clients ( 2fdb327a )

Other

dependencies: Autobump fiatVersion ( b61e752b )
dependencies: Autobump korkVersion ( 139af4a0 )
dependencies: Autobump fiatVersion ( c7f18c88 )
dependencies: Autobump korkVersion ( c8496b5d )
dependencies: Autobump fiatVersion ( 7071d6e9 )
dependencies: Autobump korkVersion ( d04c5186 )
dependencies: Autobump korkVersion ( d04c5186 )
retrofit1: revert adding Retrofit2EncodeCorrectionInterceptor to retrofit1 clients in tests as kork is updated with new constructor ( 2fdb327a )

Rosco 1.26.0

Other

dependencies: Autobump korkVersion ( 0ae53eb0 )
dependencies: Autobump korkVersion ( cac7dd3d )
dependencies: Autobump korkVersion ( 84b7fe58 )

Spinnaker Release 1.37.10

Mon, 14 Apr 2025 22:19:13 +0000

Echo 2.44.7

Fixes

retrofit2: fix google cloud build notification agent for missing Retrofit2SyncCall.execute call (#1500) ( 21721cb9 )
retrofit2: fix the issue of missing Retrofit2SyncCall.execute call in GoogleCloudBuildNotificationAgent ( 21721cb9 )

Other

retrofit2: add a test to demonstrate the issue of missing Retrofit2SyncCall.execute call in GoogleCloudBuildNotificationAgent ( 21721cb9 )

Spinnaker Release 1.37.9

Wed, 09 Apr 2025 04:31:08 +0000

Clouddriver 5.91.6

Fixes

core/test: add a Retrofit2EncodeCorrectionInterceptor bean ( f56f4f9e )
docker/test: add a Retrofit2EncodeCorrectionInterceptor bean ( f56f4f9e )

Other

dependencies: Autobump fiatVersion ( f0abfea1 )
dependencies: Autobump korkVersion ( 1e70bbdd )
dependencies: Autobump korkVersion ( f56f4f9e )
dependencies: Autobump korkVersion ( f56f4f9e )

Echo 2.44.6

Fixes

retrofit: address remnants of retrofit1 like TypedInput, TypedByteArray etc (#1493) ( 4212e89c )
retrofit: address remnants of retrofit1 like TypedInput, TypedByteArray etc ( 4212e89c )
retrofit2/test: deal with the introduction of Retrofit2EncodeCorrectionInterceptor ( 226670cc )

Other

core/test: only spin up a wiremock server once in IgorServiceTest ( 4212e89c )
dependencies: Autobump fiatVersion ( 0eac7c7c )
dependencies: Autobump korkVersion ( 9a7ef451 )
dependencies: Autobump korkVersion ( 226670cc )
dependencies: Autobump korkVersion ( 226670cc )
retrofit: add a test to demonstrate the issue of passing a TypedInput while using retrofit2 client ( 4212e89c )

Fiat 1.54.2

Other

dependencies: Autobump korkVersion ( 489b9b27 )
dependencies: Autobump korkVersion ( 1f5fd73a )

Front50 2.38.2

Other

dependencies: Autobump fiatVersion ( 96c758f4 )
dependencies: Autobump korkVersion ( 4e935e19 )
dependencies: Autobump korkVersion ( 027cb28f )

Gate 6.66.6

Fixes

retrofit2/test: deal with the introduction of Retrofit2EncodeCorrectionInterceptor ( e4c1a499 )

Other

dependencies: Autobump fiatVersion ( 57ed6109 )
dependencies: Autobump korkVersion ( a7dbb54d )
dependencies: Autobump korkVersion ( e4c1a499 )
dependencies: Autobump korkVersion ( e4c1a499 )

Igor 4.19.2

Other

dependencies: Autobump fiatVersion ( db63b98b )
dependencies: Autobump korkVersion ( 70375f29 )
retrofit1: make sure Retrofit2EncodeCorrectionInterceptor is not included in the retrofit1 clients ( a34671ba )

Kayenta 2.44.2

Other

dependencies: Autobump orcaVersion ( 343b06ec )

Orca 8.61.2

Fixes

retrofit1: exclude Retrofit2EncodeCorrectionInterceptor from the retrofit1 clients (#4857) ( ced52554 )
retrofit1: exclude Retrofit2EncodeCorrectionInterceptor from the retrofit1 clients ( ced52554 )

Other

dependencies: Autobump fiatVersion ( 38b4af39 )
dependencies: Autobump korkVersion ( b7223b9f )
retrofit1: revert adding Retrofit2EncodeCorrectionInterceptor to retrofit1 clients in tests as kork is updated with new constructor ( ced52554 )

Rosco 1.23.1

Other

dependencies: Autobump korkVersion ( 1b72b865 )
dependencies: Autobump korkVersion ( 64e90cc2 )

Spinnaker Release 1.37.8

Sun, 23 Mar 2025 02:46:00 +0000

Clouddriver 5.91.5

Other

dependencies: Autobump fiatVersion ( a34c2759 )

Echo 2.44.5

Other

dependencies: Autobump fiatVersion ( 0685f7a8 )

Fiat 1.54.1

Fixes

github: fix the error where if the baseUrl of the Github client has multiple slashes and the end point start with a slash, the resultant api url leaves that part the base url coming after first slash. ( 6a2024ec )
retrofit2: fix multiple slash issue in baseUrl of retrofit2 client (#1206) ( 6a2024ec )

Other

api: refactor retrofit2 client configuration for FiatService to fix any issues that may occur if the base url has multiple slashes ( 6a2024ec )
github: add a test to demonstrate an error scenario where if the baseUrl of the Github client has multiple slashes and the end point start with a slash ( 6a2024ec )
web: refactor retrofit2 client configuration for IgorApi, ClouddriverApi and Front50Api to fix any issues that may occur if the base url has multiple slashes ( 6a2024ec )

Front50 2.38.1

Other

dependencies: Autobump fiatVersion ( a038589e )

Gate 6.66.5

Other

dependencies: Autobump fiatVersion ( 2cc76390 )

Igor 4.19.1

Other

dependencies: Autobump fiatVersion ( 9a2ad8b5 )

Kayenta 2.44.1

Other

dependencies: Autobump orcaVersion ( 74292755 )

Orca 8.61.1

Other

dependencies: Autobump fiatVersion ( 1f8d42e9 )

Spinnaker Release 1.37.7

Tue, 18 Mar 2025 18:17:36 +0000

Clouddriver 5.91.4

Fixes

docker: resolve the issue of Unrecognized field "child" (#6359) ( b79b25c6 )
docker: resolve the issue of Failed to parse ResponseBody : Unrecognized field "child" when google cloud artifact registry responds with additional fields upon invoking tags list api ( b79b25c6 )

Other

docker: add a test to demonstrate the issue of Failed to parse ResponseBody : Unrecognized field "child" ( b79b25c6 )

Spinnaker Release 1.37.6

Wed, 12 Mar 2025 22:15:45 +0000

Clouddriver 5.91.3

Fixes

docker: resolve the issue of double encoding while making the next call to ECR’s tags list (#6357) ( dd4791f9 )
docker: resolve the issue of double encoding contained in the ECR’s next link header causing the Retrofit2 client to fail due to error code 405 and Message: Method Not Allowed. ( dd4791f9 )

Other

docker: add test to demonstrate the issue of double encoding of query parameter when the next link from a docker registry like ECR responds with an encoded url. ( dd4791f9 )

Deck 3.20.1

Fixes

gcp: fixing existing test + adding one test and updating credentials.json (#10166) ( b3f52630 )

Spinnaker Release 1.37.5

Fri, 07 Mar 2025 20:45:13 +0000

Clouddriver 5.91.2

Fixes

docker: fix retrofit2 docker client which is replacing ? with %3F causing api failure (#6354) ( fd29d63d )
docker: fix the issue of retrofit2 replacing ? with %3F causing api failure with 400 ( fd29d63d )
docker: address review comments on the fix to the issue of retrofit2 replacing ? with %3F causing api failure with 400 ( fd29d63d )

Other

docker: add two test classes, one to demonstrate how real docker registry apis can be accessed using retrofit2 client and another to demonstrate the issue of retrofit2 replacing ? with %3F causing api failure with 400 ( fd29d63d )

Spinnaker Release 1.37.4

Wed, 05 Mar 2025 21:18:21 +0000

Echo 2.44.4

Fixes

notifications: fix MicrosoftTeamsConfig which has unused retrofit1 parameters (#1485) ( aa889534 )

Spinnaker Release 1.37.3

Tue, 04 Mar 2025 15:26:15 +0000

Echo 2.44.3

Fixes

notifications: add Retrofit2SyncCall.execute to BearychatService in BearychatNotificationService (#1482) ( 6762b0ab )
notifications: add Retrofit2SyncCall.execute to BearychatService in BearychatNotificationService ( 6762b0ab )

Other

notifications: add a test to demonstrate the missing Retrofit2SyncCall.execute calls in BearychatNotificationService ( 6762b0ab )

Gate 6.66.4

Fixes

web: fix the mismatch in return types of EchoService.postEvent api stub and the actual api from echo (#1885) ( 826286d7 )
web: fix the mismatch in return types of EchoService.postEvent api stub and the actual api from echo. ( 826286d7 )

Other

web: add a test to demonstrate the mismatch in return types of EchoService.postEvent api stub and the actual api from echo. ( 826286d7 )

Spinnaker Release 1.37.2

Sat, 01 Mar 2025 20:48:42 +0000

Echo 2.44.2

Fixes

rest: add Retrofit2SyncCall.execute to RestService in RestEventService (#1480) ( 9d3a7dc4 )
rest: add Retrofit2SyncCall.execute to RestService in RestEventService ( 9d3a7dc4 )

Other

rest: add a test to demonstrate that RestEventService.sendEvent is failing to make the RestService.recordEvent api call ( 9d3a7dc4 )

Gate 6.66.3

Fixes

web: fix the mismatches in the return types of APIs in gate and orca (#1883) ( de72fa6e )
web: fix the mismatches in the return types of apis in gate and orca for delete, resume, cancel and pause operations of a pipeline. ( de72fa6e )
web: add Retrofit2SyncCall.execute to ClouddriverService in CredentialsController (#1881) ( 2db175e4 )
web: add Retrofit2SyncCall.execute to ClouddriverService in CredentialsController ( 2db175e4 )

Other

web: add a test to demonstrate the mismatch in api response types of gate and orca when delete pipeline execution api is invoked ( de72fa6e )
web: add a test to demonstrate the retrofit error that occurs when /credentials/type/{accountType} is invoked ( 2db175e4 )
web/test: mock DefaultProviderLookupService in PipelineServiceTest ( de72fa6e )
web/test: remove request id header from PipelineServiceTest ( de72fa6e )
web/test: add X-SPINNAKER-USER and X-SPINNAKER-ACCOUNTS headers ( de72fa6e )

Spinnaker Release 1.37.1

Fri, 28 Feb 2025 00:30:49 +0000

Clouddriver 5.91.1

Fixes

clouddriver-google: Fix logic when Instance Types are available only in selected Zones/Regions (#6351) ( 7824652f )

Echo 2.44.1

Fixes

retrofit2: fix A @path parameter must not come after a @Query error (#1478) ( a410556a )
retrofit2: fix A @Path parameter must not come after a @Query error ( a410556a )
retrofit2: fix baseUrl must end in / error (#1476) ( 85b8dbde )
retrofit2: fix the following error by adding trailing / in the baseUrl and removing leading / in the end point: ( 85b8dbde )
retrofit2: fix RestService by replacing POST mapping from / to . and add a test class to demonstrate the behaviour. ( 85b8dbde )

Other

retrofit2: add a test to demonstrate the following error: ( a410556a )
retrofit2: add a test to demonstrate the error: java.lang.IllegalArgumentException: baseUrl must end in /. ( 85b8dbde )

Gate 6.66.1

Fixes

retrofit2: fix retrofit2 issues (#1875) ( 0da41f43 )
retrofit2: fix non-generics QueryMap which causes the following error: ( 0da41f43 )
retrofit2: fix A @Path parameter must not come after a @Query error ( 0da41f43 )
web: add Retrofit2SyncCall.execute to BakeService (#1879) ( c22cc721 )
web: add Retrofit2SyncCall.execute to BakeService ( c22cc721 )
web: make type of additionalFilters in ImageController.findImages (#1877) ( 70da3729 )
web: make type of additionalFilters in ImageController.findImages ( 70da3729 )

Other

retrofit2: add test to demonstrate the following error when QueryMap is used without generics: ( 0da41f43 )
web: use constructor injection in BakeService ( c22cc721 )
web: demonstrate behavior of BakeService ( c22cc721 )
web: demonstrate behavior of ImageController.findImages ( 70da3729 )

Spinnaker Release 1.37.0

Mon, 24 Feb 2025 23:42:26 +0000

Changelog

Clouddriver

https://github.com/spinnaker/clouddriver/pull/6342 adds retry logic to AWS credential parsing, controlled with these new configuration properties and their defaults:

aws:
  loadAccounts:
    maxRetries: 10
    backOffInMs: 5000
    exponentialBackoff: false
    exponentialBackoffMultiplier: 2
    exponentialBackOffIntervalMs: 10000

https://github.com/spinnaker/clouddriver/pull/6344 makes the duration of assume role sessions configurable via a new per-account propery sessionDurationSeconds and

aws:
  defaultSessionDurationSeconds: (no default value)

The per-account property takes precedence. If neither aws.defaultSessionDurationSeconds nor a per-account sessionDurationSeconds is set, the duration of assume role sessions is the default provided by the aws sdk. In version 1.12.261, that’s 900 seconds.

Spinnaker Release 1.34.6

Thu, 23 Jan 2025 17:06:54 +0000

Clouddriver 5.85.5

Features

aws: CleanupAlarmsAgent with an optional user-defined name pattern (#6317) ( c2ba7f0f )

Fixes

cloudfoundry: Update ProcessStats model due to capi-1.84.0 changes (#6283) ( ea908a3b )
mergify: Mergify config needs adjusting for latest mergify releases (#6321) ( 5a86b8a3 )
mergify: Mergify config needs adjusting for latest mergify releases ( 5a86b8a3 )
mergify: Add integration test checks ( 5a86b8a3 )
mergify: Add integration test checks ( 5a86b8a3 )
mergify: Add integration test checks ( 5a86b8a3 )
mergify: Use just queue_conditions ( 5a86b8a3 )

Deck 3.17.3

Fixes

aws: Fix userData getting lost when cloning an AWS server group that uses launch templates (#6771) (#10132) ( ba132191 )

Kayenta 2.40.4

Other

dependencies: Autobump orcaVersion ( 2a94b8b3 )

Orca 8.51.3

Fixes

ecs: Docker image extraction from context (#4812) ( 647d692a )

Rosco 1.20.3

Fixes

gceBakeHandler: Updating Image name pattern to match googlecompute pre/post 1.1.2 plugin (#1122) ( 0a51cd24 )

Spinnaker Release 1.35.5

Wed, 22 Jan 2025 23:40:47 +0000

Clouddriver 5.86.4

Features

aws: CleanupAlarmsAgent with an optional user-defined name pattern (#6317) ( fb1850b9 )

Fixes

cloudfoundry: Update ProcessStats model due to capi-1.84.0 changes (#6283) ( c83c7c03 )
mergify: Mergify config needs adjusting for latest mergify releases (#6321) ( 9c064d10 )
mergify: Mergify config needs adjusting for latest mergify releases ( 9c064d10 )
mergify: Add integration test checks ( 9c064d10 )
mergify: Add integration test checks ( 9c064d10 )
mergify: Add integration test checks ( 9c064d10 )
mergify: Use just queue_conditions ( 9c064d10 )

Deck 3.18.1

Fixes

aws: Fix IPv6 addresses being incorrectly associated when cloning server groups that have launch templates enabled (#6979) (#10142) ( d2e3a0c4 )
aws: Fix userData getting lost when cloning an AWS server group that uses launch templates (#6771) (#10132) ( a6921063 )

Kayenta 2.41.1

Other

dependencies: Autobump orcaVersion ( 17c02a48 )

Orca 8.54.1

Fixes

ecs: Docker image extraction from context (#4812) ( 6768b787 )
pipelineRef: add resolvedExpectedArtifacts from pipelineTrigger to PipelineRefTrigger (#4816) ( f7c2dd3f )
pipelineRef: add resolvedExpectedArtifacts from pipelineTrigger to PipelineRefTrigger ( f7c2dd3f )
pipelineRef: add tests around PipelineRefTrigger ( f7c2dd3f )

Rosco 1.21.1

Fixes

gceBakeHandler: Updating Image name pattern to match googlecompute pre/post 1.1.2 plugin (#1122) ( 59a8c79d )

Spinnaker Release 1.36.1

Wed, 22 Jan 2025 20:57:09 +0000

Clouddriver 5.90.1

Features

aws: CleanupAlarmsAgent with an optional user-defined name pattern (#6317) ( 966f4e8a )

Fixes

ecs: Alarms with custom dimensions should be processed (#6324) ( 00824a96 )
ecs: Cloudwatch alarms cleanup on destroy ecs group (#6315) ( 8264ff4f )
google: Add partner metadata on instanceTemplate properties (#6334) ( e7598016 )
google: include partnerMetadata in InstanceTemplates ( e7598016 )
google: remove default view and add tests ( e7598016 )
google: format comment ( e7598016 )
google: remove unused imports ( e7598016 )
google: make FULL the default view in instanceTemplate client ( e7598016 )
mergify: Mergify config needs adjusting for latest mergify releases (#6321) ( 7daeb3b8 )
mergify: Mergify config needs adjusting for latest mergify releases ( 7daeb3b8 )
mergify: Add integration test checks ( 7daeb3b8 )
mergify: Add integration test checks ( 7daeb3b8 )
mergify: Add integration test checks ( 7daeb3b8 )
mergify: Use just queue_conditions ( 7daeb3b8 )
openapi: Rewrite Swagger to OpenAPI annotations (#6309) ( ec28083d )
openapi: Rewrite Swagger to OpenAPI annotations ( ec28083d )

Other

dependencies: Autobump fiatVersion ( c89e9a0b )
dependencies: Autobump korkVersion ( 472ffadd )

Deck 3.19.1

Fixes

google: Add partner metadata on clone (#10161) ( 5dde11ff )
google: populate resourceManagerTags & partnerMetadata when cloning server group ( 5dde11ff )
google: add logs for debug ( 5dde11ff )
google: populate resourceManagerTags & partnerMetadata from launchConfig when clone serverGroup ( 5dde11ff )

Echo 2.43.1

Other

dependencies: Autobump fiatVersion ( 4a009d6a )
dependencies: Autobump korkVersion ( 0c275bd1 )

Fiat 1.51.1

Fixes

openapi: Rewrite Swagger to OpenAPI annotations (#1192) ( be2a82b2 )
openapi: Rewrite Swagger to OpenAPI annotations ( be2a82b2 )

Other

dependencies: Autobump korkVersion ( 68c63dd2 )
deps: bump latest kork version ( be2a82b2 )

Front50 2.37.1

Fixes

openapi: Rewrite Swagger to OpenAPI annotations (#1514) ( 9e8f1828 )
openapi: Rewrite Swagger to OpenAPI annotations ( 9e8f1828 )

Other

dependencies: Autobump fiatVersion ( 33a99894 )
dependencies: Autobump korkVersion ( 1ea7a5e3 )
deps: bump latest kork version ( 9e8f1828 )

Gate 6.64.1

Fixes

openapi: Uses openrewrite to convert swagger to openapi annotations (#1813) ( 039fd79a )
openapi: Uses openrewrite to convert owagger to openapi annotations ( 039fd79a )
swagger: Adds property allow swagger generation ( 039fd79a )

Other

dependencies: Autobump fiatVersion ( 83457207 )
dependencies: Autobump korkVersion ( a9316bc6 )
deps: bump latest kork version ( 039fd79a )
swagger: Code minus kork constraints to switch to openapi. ( 039fd79a )

Igor 4.18.1

Other

dependencies: Autobump fiatVersion ( 2f3de993 )
dependencies: Autobump korkVersion ( 8f5dbb23 )

Kayenta 2.42.1

Other

dependencies: Autobump orcaVersion ( 41525f2b )
upgrade: Migrate to openapi swagger spec (#1046) ( 66269f74 )

Orca 8.57.1

Fixes

ecs: Docker image extraction from context (#4812) ( 87141f21 )
pipelineRef: add resolvedExpectedArtifacts from pipelineTrigger to PipelineRefTrigger (#4816) ( b03087e4 )
pipelineRef: add resolvedExpectedArtifacts from pipelineTrigger to PipelineRefTrigger ( b03087e4 )
pipelineRef: add tests around PipelineRefTrigger ( b03087e4 )

Other

dependencies: Autobump fiatVersion ( 6228405f )
dependencies: Autobump korkVersion ( 2569bdec )

Rosco 1.22.1

Fixes

gceBakeHandler: Updating Image name pattern to match googlecompute pre/post 1.1.2 plugin (#1122) ( eccbf4d9 )
openapi: Rewrite Swagger to OpenAPI annotations (#1126) ( a3cb6e89 )
openapi: Rewrite Swagger to OpenAPI annotations ( a3cb6e89 )

Other

dependencies: Autobump korkVersion ( 360c4a9a )
deps: bump latest kork version ( a3cb6e89 )

Spinnaker Release 1.36.0

Wed, 20 Nov 2024 15:57:38 +0000

Changelog

Java upgrades

Java 17 is now the default source and target. Java 11 support has been removed entirely. Please note you may need to add the following JAVA_OPTS options: --add-exports=java.base/sun.security.x509=ALL-UNNAMED --add-exports=java.base/sun.security.pkcs=ALL-UNNAMED --add-exports=java.base/sun.security.rsa=ALL-UNNAMED to clouddriver if using GCP accounts due to credentials parsing of certificates. These can set in the service-settings config . These configs are likely to be added to the defaults in all future releases

Kleat is deprecated

Kleat as an initial attempt to replace halyard is being deprecated and no longer updated or supported. It’s recommended to look at spinnaker-kustomize repo as an alternative or stay with halyard at this time.

Spinnaker Release 1.35.4

Tue, 27 Aug 2024 19:35:53 +0000

Clouddriver 5.86.3

Fixes

aws: Fix AWS CLI v2 for Alpine Linux (#6279) ( 59c86f4d )
aws: Fix AWS CLI v2 for Alpine Linux ( 59c86f4d )

Spinnaker Release 1.35.3

Fri, 23 Aug 2024 17:07:12 +0000

Front50 2.33.1

Fixes

front50-gcs: Fix ObjectType filenames for GCS Front50 persistent store (#1493) ( 210501bf )
gha: only bump halyard on master (#1490) ( 6d09e862 )

Spinnaker Release 1.34.5

Fri, 23 Aug 2024 16:58:07 +0000

Front50 2.32.2

Fixes

front50-gcs: Fix ObjectType filenames for GCS Front50 persistent store (#1493) ( 25bda17a )
gha: only bump halyard on master (#1490) ( 27526ee8 )

Spinnaker Release 1.35.2

Tue, 20 Aug 2024 20:48:23 +0000

Note: Broken Functionality

Spinnaker 1.35.2 includes Front50 2.33.0 which breaks loading of Front50 objects:

When GCS is used as a persistent store
When GCS is used in a dual repository configuration

Clouddriver 5.86.2

Fixes

install: Fix Debian post installation script when awscli2 is already installed or the installation failed previously (#6276) ( f4dbb7cd )

Spinnaker Release 1.35.1

Mon, 19 Aug 2024 22:35:01 +0000

Note: Broken Functionality

Spinnaker 1.35.1 includes Front50 2.33.0 which breaks loading of Front50 objects:

When GCS is used as a persistent store
When GCS is used in a dual repository configuration

Clouddriver 5.86.1

Fixes

gha: remove whitespace from BRANCH in release.yml (#6271) ( c32a5f25 )
gha: only bump halyard on master (#6268) ( 73b6e032 )
install: Fixed Debian post install script for aws-iam-authenticator (#6274) ( 6bcea393 )

Spinnaker Release 1.34.4

Sun, 18 Aug 2024 16:13:39 +0000

Note: Broken Functionality

Spinnaker 1.34.4 includes Front50 2.31.2 which breaks loading of Front50 objects:

When GCS is used as a persistent store
When GCS is used in a dual repository configuration

Clouddriver 5.85.4

Fixes

gha: remove whitespace from BRANCH in release.yml (#6271) ( 97f44836 )
gha: only bump halyard on master (#6268) ( 46c42ce2 )
google: fixing UpsertGoogleAutoscalingPolicyAtomicOperation missing Autowired for objectMapper and cacheView (#6237) ( f3d9bcfe )
google: adding autowired for cacheview and objectmapper ( f3d9bcfe )
google: adding autowired for cacheview and objectmapper ( f3d9bcfe )

Other

dependencies: Autobump fiatVersion ( a8879b89 )
dependencies: Autobump korkVersion ( f6e87b93 )
gcp: Adding STRONG_COOKIE_AFFINITY in gcp LB model (#6259) ( 52d394c0 )

Deck 3.17.2

Other

gcp: Adding STRONG_COOKIE_AFFINITY in gcp LB model (#10124) ( 71267893 )

Echo 2.41.1

Other

dependencies: Autobump fiatVersion ( 6e30ba25 )
dependencies: Autobump korkVersion ( cde85bd1 )

Fiat 1.46.1

Other

dependencies: Autobump korkVersion ( e144e4d2 )

Front50 2.32.1

Fixes

migrator: GCS to SQL migrator APPLICATION_PERMISSION objectType fix (#1466) ( f8c86dc3 )
migrator: GCS to SQL migrator APPLICATION_PERMISSION fix/refactor ( f8c86dc3 )
migrator: GCS to SQL migrator APPLICATION_PERMISSION fix/refactor ( f8c86dc3 )

Other

dependencies: Autobump fiatVersion ( 951308ec )
dependencies: Autobump korkVersion ( c74e1587 )

Gate 6.62.1

Fixes

core: remove ErrorPageSecurityFilter bean named errorPageSecurityInterceptor ( 401e7179 )
core: remove ErrorPageSecurityFilter bean named errorPageSecurityInterceptor ( 401e7179 )
web/test: stop leaking system properties from FunctionalSpec (#1798) ( 08f368ed )

Other

basic: use constructor injection in BasicAuthConfig ( 401e7179 )
dependencies: Autobump fiatVersion ( 0ee70bb6 )
dependencies: Autobump korkVersion ( a6ab4380 )
web: demonstrate bug in MultiAutoSupport ( 401e7179 )
web: verify some error handling behavior of AuthConfig ( 401e7179 )

Igor 4.16.1

Other

dependencies: Autobump fiatVersion ( f30dce4d )
dependencies: Autobump korkVersion ( 756120ac )

Kayenta 2.40.3

Fixes

stackdriver: handle null timeSeries and empty points (#1047) ( e2319493 )

Other

dependencies: Autobump orcaVersion ( 7e04fdf3 )

Orca 8.51.2

Fixes

backport: Fix tests on bad backport for search API breakage due to compression changes ( 69084612 )
sqlExecutionRepo: Return compressed columns when enabled for retrieve pipelines with configId (backport #4765) ( 69084612 )
sqlExecutionRepo: Return compressed columns when enabled for retrieve pipelines with configId ( 69084612 )

Other

dependencies: Autobump fiatVersion ( 0de6415a )
dependencies: Autobump korkVersion ( 688d2165 )

Rosco 1.20.2

Other

dependencies: Autobump korkVersion ( 8adc6983 )

Spinnaker Release 1.35.0

Fri, 16 Aug 2024 23:14:19 +0000

Note: Broken Functionality

Spinnaker 1.33.3 includes Front50 2.33.0 which breaks loading of Front50 objects:

When GCS is used as a persistent store
When GCS is used in a dual repository configuration

Changelog

Version 1.31 of Spinnaker introduced two features that were disabled by default:

echo: pipelineCache.filterFront50Pipelines

orca: front50.useTriggeredByEndpoint

Both of these features are now enabled by default.

Java 17

All Spinnaker services are now compiled by JDK 17, transpiling to Java 11 bytecode. Published images run JRE 17. In 1.36, compilation will switch to Java 17 bytecode, completing our migration to Java 17. Please continue to report issues by opening an issue in the spinnaker repository .

Spinnaker Release 1.28.10

Fri, 09 Aug 2024 02:01:39 +0000

Clouddriver 5.76.9

Other

gcp: Adding STRONG_COOKIE_AFFINITY in gcp LB model (#6259) ( 59f91b44 )

Deck 3.9.6

Fixes

lint: fixing linting erros ( 3965efb5 )
lint: fixing linting - lodash ( 3965efb5 )
prettier: fixing prettier for AdditionalFields.tsx ( 3965efb5 )
redblack: fixing redblack onchange values (#10107) ( 3965efb5 )
redblack: fixing redblack onchange values ( 3965efb5 )

Other

gcp: Adding STRONG_COOKIE_AFFINITY in gcp LB model (#10124) ( 1a0ada66 )

Kayenta 2.32.9

Fixes

mergify: fix conflicts in cherry-pick ( 7358bd38 )
stackdriver: handle null timeSeries and empty points (backport #1047) ( 7358bd38 )
stackdriver: handle null timeSeries and empty points ( 7358bd38 )

Spinnaker Release 1.34.3

Sat, 15 Jun 2024 00:23:05 +0000

Clouddriver 5.85.3

Features

build: add fiat-integration module to exercise the just-built docker imageTest docker image (#6206) ( 644ff6d7 )
build: add clouddriver-integration module to exercise the just-built docker image ( 644ff6d7 )
docker: add HEALTHCHECK ( 644ff6d7 )
gha: run integration test in pr builds ( 644ff6d7 )
gha: run integration test in branch builds ( 644ff6d7 )

Fixes

ClusterController: Fix GetClusters returning only the last 2 providers clusterNames of application (#6210) ( f8bfe246 )
docker: reduce the chance for false positives in the health check ( 644ff6d7 )
gcp: Relaxed health check for GCP accounts (#6200) ( 20fd2c89 )
liquibase: fix checkSum errors occurring with spinnaker upgrade (#6217) ( 4d1782eb )
liquibase: add validCheckSum values to fix failing changesets ( 4d1782eb )
tests: added postgres migration test ( 4d1782eb )
tests: hardcoded the docker image to create initial conditions ( 4d1782eb )
tests: refactored existing containerized integration test and added new tests for postgres and mysql (#6221) ( a46c18c2 )
web: replace deprecated spring.profiles in configuration ( 644ff6d7 )

Deck 3.17.1

Features

taskView: Implement opt-in paginated request for TaskView (#10093) ( e322eb53 )
taskView: Implement opt-in paginated request for TaskView ( e322eb53 )
tasksview: Allowing opt-in pagination for tasks view loading ( e322eb53 )

Fixes

lambda: Export LambdaRoute stage on aws module (#10116) ( af6fa426 )
lambda: Invoke stage excludedArtifactTypes not including the embedded-artifact type (#10097) ( 2433668c )
lambdaStages: Exporting Lambda stages based on the feature flag settings (#10085) ( f88b1186 )
lint: fixing linting erros ( 4911c2f1 )
lint: fixing linting - lodash ( 4911c2f1 )
pipeline: Handle render/validation when stageTimeoutMs is a Spel expression (#10103) ( 7924b110 )
pipelineGraph: Handling exception when requisiteStageRefIds is not defined (#10086) ( f825a71b )
prettier: fixing prettier for AdditionalFields.tsx ( 4911c2f1 )
redblack: fixing redblack onchange values (#10107) ( 4911c2f1 )
redblack: fixing redblack onchange values ( 4911c2f1 )

Kayenta 2.40.1

Other

dependencies: Autobump orcaVersion ( 13fe6239 )

Orca 8.51.1

Features

build: add orca-integration module to exercise the just-built docker image (#4721) ( ae787969 )
build: add orca-integration module to exercise the just-built docker image ( ae787969 )
docker: add HEALTHCHECK ( ae787969 )
gha: run integration test in pr builds ( ae787969 )
gha: run integration test in branch builds ( ae787969 )

Fixes

blueGreen: Scaling replicaSets should not be considered for deletion (#4728) ( b303a9b3 )
jenkins: Wrong Job name encoding in query params for Artifacts/Properties (#4722) ( f0a08377 )
jenkins: Wrong Job name encoding in query params for Artifacts/Properties ( f0a08377 )
jenkins: Wrong Job name encoding in query params - added Wiremock tests ( f0a08377 )
jenkins: Wrong Job name encoding in query params - fix Wiremock tests imports ( f0a08377 )
liquibase: fix checkSum errors occurring with spinnaker upgrade (#4727) ( 0c322572 )
liquibase: Fix validChecksum errors occurred due to liquibase upgrade ( 0c322572 )
tests: Add new integration test for postgres migration - PostgresMigrationContainerTest ( 0c322572 )
tests: add new containerized integration tests to run orca with mysql and postgres (#4736) ( 680121f4 )

Spinnaker Release 1.33.3

Fri, 14 Jun 2024 17:17:53 +0000

Note: Broken Functionality

Spinnaker 1.33.3 includes Front50 2.31.2 which breaks loading of Front50 objects:

When GCS is used as a persistent store
When GCS is used in a dual repository configuration

Clouddriver 5.83.4

Features

build: add fiat-integration module to exercise the just-built docker imageTest docker image (#6206) ( a212752c )
build: add clouddriver-integration module to exercise the just-built docker image ( a212752c )
docker: add HEALTHCHECK ( a212752c )
gha: run integration test in pr builds ( a212752c )
gha: run integration test in branch builds ( a212752c )

Fixes

ClusterController: Fix GetClusters returning only the last 2 providers clusterNames of application (#6210) ( cdc82e64 )
docker: reduce the chance for false positives in the health check ( a212752c )
gcp: Relaxed health check for GCP accounts (#6200) ( a047c081 )
liquibase: fix checkSum errors occurring with spinnaker upgrade (#6217) ( e764f9f8 )
liquibase: add validCheckSum values to fix failing changesets ( e764f9f8 )
tests: added postgres migration test ( e764f9f8 )
tests: hardcoded the docker image to create initial conditions ( e764f9f8 )
tests: refactored existing containerized integration test and added new tests for postgres and mysql (#6221) ( dd96b48b )
web: replace deprecated spring.profiles in configuration ( a212752c )

Deck 3.16.2

Features

taskView: Implement opt-in paginated request for TaskView (#10093) ( a7116baa )
taskView: Implement opt-in paginated request for TaskView ( a7116baa )
tasksview: Allowing opt-in pagination for tasks view loading ( a7116baa )

Fixes

lambda: Export LambdaRoute stage on aws module (#10116) ( 4cb68a17 )
lambda: Invoke stage excludedArtifactTypes not including the embedded-artifact type (#10097) ( 9f57b2ba )
lambdaStages: Exporting Lambda stages based on the feature flag settings (#10085) ( 102b439b )
lint: fixing linting erros ( 94cfdf99 )
lint: fixing linting - lodash ( 94cfdf99 )
pipeline: Handle render/validation when stageTimeoutMs is a Spel expression (#10103) ( 96a3527c )
pipelineGraph: Handling exception when requisiteStageRefIds is not defined (#10086) ( a78669a7 )
prettier: fixing prettier for AdditionalFields.tsx ( 94cfdf99 )
redblack: fixing redblack onchange values (#10107) ( 94cfdf99 )
redblack: fixing redblack onchange values ( 94cfdf99 )

Front50 2.31.2

Fixes

migrator: GCS to SQL migrator APPLICATION_PERMISSION objectType fix (#1466) ( 121849e3 )
migrator: GCS to SQL migrator APPLICATION_PERMISSION fix/refactor ( 121849e3 )
migrator: GCS to SQL migrator APPLICATION_PERMISSION fix/refactor ( 121849e3 )

Kayenta 2.39.3

Other

dependencies: Autobump orcaVersion ( b73de319 )

Orca 8.48.3

Features

build: add orca-integration module to exercise the just-built docker image (#4721) ( 8269f0da )
build: add orca-integration module to exercise the just-built docker image ( 8269f0da )
docker: add HEALTHCHECK ( 8269f0da )
gha: run integration test in pr builds ( 8269f0da )
gha: run integration test in branch builds ( 8269f0da )

Fixes

blueGreen: Scaling replicaSets should not be considered for deletion (#4728) ( 05d8b56a )
check-pre-condition: CheckPrecondition doesn’t evaluate expression correctly after upstream stages get restarted (#4682) ( b4263145 )
jenkins: Wrong Job name encoding in query params for Artifacts/Properties (#4722) ( d3d70837 )
jenkins: Wrong Job name encoding in query params for Artifacts/Properties ( d3d70837 )
jenkins: Wrong Job name encoding in query params - added Wiremock tests ( d3d70837 )
jenkins: Wrong Job name encoding in query params - fix Wiremock tests imports ( d3d70837 )
liquibase: fix checkSum errors occurring with spinnaker upgrade (#4727) ( 22e7112a )
liquibase: Fix validChecksum errors occurred due to liquibase upgrade ( 22e7112a )
tests: Add new integration test for postgres migration - PostgresMigrationContainerTest ( 22e7112a )
tests: add new containerized integration tests to run orca with mysql and postgres (#4736) ( 9c391ae5 )

Spinnaker Release 1.28.9

Wed, 08 May 2024 18:17:49 +0000

Clouddriver 5.76.8

Fixes

gcp: Relaxed health check for GCP accounts (backport #6200) ( 95d0e683 )
gcp: Relaxed health check for GCP accounts ( 95d0e683 )

Kayenta 2.32.8

Other

dependencies: Autobump orcaVersion ( 8f252267 )

Orca 8.24.9

Features

servergroup: Allow users to opt-out of the target desired size check when verifying if the instances scaled up or down successfully (#4649) ( 6a375967 )
servergroup: Allow users to opt-out of the target desired size check when verifying if the instances scaled up or down successfully ( 6a375967 )

Spinnaker Release 1.34.2

Mon, 22 Apr 2024 18:23:54 +0000

Note: Broken Functionality

Spinnaker 1.33.0 upgrades to liquibase 4.24.0 which breaks the following scenarios when using postgres:

new installation with versions 1.33.0, 1.33.1, 1.34.0 & 1.34.1
upgrade/migration from versions < 1.33.0 to 1.33.0/1.33.1/1.33.2/1.34.0/1.34.1/1.34.2

These scenarios work from Spinnaker 1.33.3 (and above) and Spinnaker 1.34.3 (and above).

See https://github.com/spinnaker/spinnaker/issues/6941 and https://github.com/spinnaker/spinnaker/issues/6942 for more details.

Clouddriver 5.85.2

Fixes

databaseChangeLog: fix for ‘addAfterColumn is not allowed on postgresql’ (#6194) ( ab0d436c )

Spinnaker Release 1.33.2

Mon, 22 Apr 2024 18:10:25 +0000

Note: Broken Functionality

Spinnaker 1.33.0 upgrades to liquibase 4.24.0 which breaks the following scenarios when using postgres:

new installation with versions 1.33.0, 1.33.1, 1.34.0 & 1.34.1
upgrade/migration from versions < 1.33.0 to 1.33.0/1.33.1/1.33.2/1.34.0/1.34.1/1.34.2

These scenarios work from Spinnaker 1.33.3 (and above) and Spinnaker 1.34.3 (and above).

See https://github.com/spinnaker/spinnaker/issues/6941 and https://github.com/spinnaker/spinnaker/issues/6942 for more details.

Clouddriver 5.83.2

Fixes

databaseChangeLog: fix for ‘addAfterColumn is not allowed on postgresql’ (#6194) ( 891edd37 )

Spinnaker Release 1.34.1

Thu, 18 Apr 2024 21:49:40 +0000

Note: Broken Functionality

Spinnaker 1.33.0 upgrades to liquibase 4.24.0 which breaks the following scenarios when using postgres:

new installation with versions 1.33.0, 1.33.1, 1.34.0 & 1.34.1
upgrade/migration from versions < 1.33.0 to 1.33.0/1.33.1/1.33.2/1.34.0/1.34.1/1.34.2

These scenarios work from Spinnaker 1.33.3 (and above) and Spinnaker 1.34.3 (and above).

See https://github.com/spinnaker/spinnaker/issues/6941 and https://github.com/spinnaker/spinnaker/issues/6942 for more details.

Clouddriver 5.85.1

Other

dependencies: Autobump korkVersion (#6183) ( 79923ed2 )
deps: remove duplicate/old fiatVersion (#6191) ( 54f32e3c )

Rosco 1.20.1

Fixes

install: Removed install_aws_cli2 function from Debian post installation script which installs a Debian package within a Debian package causing errors, as well as errors when an aws cli is already installed (#6945) (#1088) ( 626849fb )

Spinnaker Release 1.33.1

Thu, 18 Apr 2024 18:42:10 +0000

Note: Broken Functionality

Spinnaker 1.33.0 upgrades to liquibase 4.24.0 which breaks the following scenarios when using postgres:

new installation with versions 1.33.0, 1.33.1, 1.34.0 & 1.34.1
upgrade/migration from versions < 1.33.0 to 1.33.0/1.33.1/1.33.2/1.34.0/1.34.1/1.34.2

These scenarios work from Spinnaker 1.33.3 (and above) and Spinnaker 1.34.3 (and above).

See https://github.com/spinnaker/spinnaker/issues/6941 and https://github.com/spinnaker/spinnaker/issues/6942 for more details.

Clouddriver 5.83.1

Fixes

fix: Change the agent type name to not include the account name since this would generate LOTS of tables and cause problems long term (#6158) ( 8f414510 )
aws: Fix bug in AWS provider after Groovy 3 upgrade (#6142) ( 962724c0 )
aws: Fix bug in AWS provider after Groovy 3 upgrade ( 962724c0 )
google: introduce explicit constructor and initialization of inner class members (#6184) ( 0dd04c5c )
provider/docker: Support multiple challenges from WWW-Authenticate header (#6139) ( 54856aa9 )
provider/docker: Support multiple challenges from WWW-Authenticate header ( 54856aa9 )

Other

dependencies: Autobump fiatVersion ( 2c0fbc02 )
dependencies: Autobump korkVersion ( 3eda2f94 )
provider/docker: Add test for WWW-Authenticate header parsing ( 54856aa9 )

Deck 3.16.1

Fixes

runJobs: Persist External Log links after the deletion of the pods (#10081) ( 1c5a30b6 )
runJobs: Persist External Log links after the deletion of the pods ( 1c5a30b6 )
runJobs: Persist External Log links after the deletion of the pods ( 1c5a30b6 )

Echo 2.40.2

Features

jenkins: Enable Jenkins job triggers for jobs in sub-folders (#1373) ( 04f380b6 )

Fixes

jenkins: Enable properties and artifacts with job name as query parameter (#1393) ( abce0915 )

Other

dependencies: Autobump fiatVersion ( 4ea40c9c )
dependencies: Autobump korkVersion ( acf2b925 )

Fiat 1.43.1

Other

dependencies: Autobump korkVersion ( 55d6f23d )

Front50 2.31.1

Other

dependencies: Autobump fiatVersion ( 25bc224b )
dependencies: Autobump korkVersion ( b8064e9d )

Gate 6.61.1

Fixes

fix: Fix git trigger issue caused by a misconfig of the object mapper when creating the echo retrofit service (#1756) ( 7e11a38d )

Other

dependencies: Autobump fiatVersion ( ae4dfc5e )
dependencies: Autobump korkVersion ( fbef4d1b )

Igor 4.15.1

Features

jenkins: Enable Jenkins job triggers for jobs in sub-folders (#1204) ( 46230e88 )

Fixes

jenkins: Enable properties and artifacts with job name as query parameter (#1230) ( 5648c179 )

Other

dependencies: Autobump fiatVersion ( 91ca1705 )
dependencies: Autobump korkVersion ( 06a5d434 )

Kayenta 2.39.2

Other

dependencies: Autobump orcaVersion ( f12081e6 )
dependencies: Autobump orcaVersion ( 26ffd01d )

Orca 8.48.2

Features

jenkins: Enable Jenkins job triggers for jobs in sub-folders (#4618) ( 56a85548 )
jenkins: Enable Jenkins job triggers for jobs in sub-folders ( 56a85548 )
jenkins: initiate flag to false in tests ( 56a85548 )
servergroup: Allow users to opt-out of the target desired size check when verifying if the instances scaled up or down successfully (#4649) ( fd27f46e )
servergroup: Allow users to opt-out of the target desired size check when verifying if the instances scaled up or down successfully ( fd27f46e )

Fixes

SqlExecutionRepository: fixed bug in sql repository in orca-sql … (backport #4697) ( f3e30b31 )
SqlExecutionRepository: fixed bug in sql repository in orca-sql … ( f3e30b31 )
SqlExecutionRepository: fixed bug in sql repository in orca-sql module ( f3e30b31 )
explicitRollback: Add configurable timeout for serverGroup lookup from Clouddriver API (#4686) ( ee0ee775 )
explicitRollback: Add configurable timeout for serverGroup rollback from Clouddriver API ( ee0ee775 )
explicitRollback: Fix tests ( ee0ee775 )
explicitRollback: Add configurable timeout for serverGroup lookup from Clouddriver API ( ee0ee775 )
explicitRollback: Add configurable timeout for serverGroup lookup from Clouddriver API ( ee0ee775 )
explicitRollback: Add configurable timeout for serverGroup lookup from Clouddriver API ( ee0ee775 )
jenkins: Enable properties and artifacts with job name as query parameter (#4661) ( 750adb94 )
jenkins: Enable properties and artifacts with job name as query parameter ( 750adb94 )
jenkins: Enable properties and artifacts with job name as query parameter ( 750adb94 )
jooq: Refactor query for execution history retrieval ( 895cdce7 )
queue: Fix ZombieExecutionCheckingAgent to handle queues with more than 100 items (#4648) ( e5960bb4 )
sql: Selecting only necessary fiels ( 895cdce7 )
sql/test: remove compression-related tests ( f3e30b31 )

Other

dependencies: Autobump fiatVersion ( 7799f041 )
dependencies: Autobump korkVersion ( 8ba98465 )
sql: demonstrate behavior of retrievePipelinesForApplication ( f3e30b31 )
sql: Optimise searchForPipelinesByTrigger LIMIT and OFFSET SQL query (#4698) ( 895cdce7 )

Rosco 1.19.1

Other

dependencies: Autobump korkVersion ( 81d309c6 )

Spinnaker Release 1.34.0

Wed, 17 Apr 2024 06:40:05 +0000

Changelog

Note: Broken Functionality

Spinnaker 1.33.0 upgrades to liquibase 4.24.0 which breaks the following scenarios when using postgres:

new installation with versions 1.33.0, 1.33.1, 1.34.0 & 1.34.1
upgrade/migration from versions < 1.33.0 to 1.33.0/1.33.1/1.33.2/1.34.0/1.34.1/1.34.2

These scenarios work from Spinnaker 1.33.3 (and above) and Spinnaker 1.34.3 (and above).

See https://github.com/spinnaker/spinnaker/issues/6941 and https://github.com/spinnaker/spinnaker/issues/6942 for more details.

Note: This release requires Halyard version 1.45.0 or later.

This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. This section provides a summary of notable improvements followed by the comprehensive changelog.

Spinnaker Release 1.32.4

Fri, 08 Mar 2024 22:39:09 +0000

Clouddriver 5.82.2

Features

gcp: provide a configurable option to bypass gcp account health check. (backport #6093) ( fdb3ac2a )
gcp: provide a configurable option to bypass gcp account health check. ( fdb3ac2a )
gcp: replace with in-line check solution. ( fdb3ac2a )

Fixes

fix: Change the agent type name to not include the account name since this would generate LOTS of tables and cause problems long term (#6158) ( 28295830 )
fix: (kork) Artifact store with SPeL expressions bypasses the artifact store to return the artifact. ( Backport via kork )

Other

dependencies: Autobump fiatVersion ( 03342d39 )
dependencies: Autobump korkVersion ( bfebd447 )

Echo 2.39.1

Features

jenkins: Enable Jenkins job triggers for jobs in sub-folders (#1373) ( f96eee33 )

Fixes

jenkins: Enable properties and artifacts with job name as query parameter (#1393) ( d5ebde4c )

Other

dependencies: Autobump fiatVersion ( 34cfae9a )
dependencies: Autobump korkVersion ( dc3c3b25 )

Fiat 1.42.1

Other

dependencies: Autobump korkVersion ( 1ba9526d )

Front50 2.30.2

Other

dependencies: Autobump fiatVersion ( 9bb418e3 )
dependencies: Autobump korkVersion ( ea6394eb )

Gate 6.60.2

Fixes

fix: Fix git trigger issue caused by a misconfig of the object mapper when creating the echo retrofit service (#1756) ( edc09af8 )

Other

dependencies: Autobump fiatVersion ( a40c30f2 )
dependencies: Autobump korkVersion ( 5b4a9e34 )

Igor 4.13.4

Features

jenkins: Enable Jenkins job triggers for jobs in sub-folders (#1204) ( d1b12f8a )

Fixes

jenkins: Enable properties and artifacts with job name as query parameter (#1230) ( 667a68fa )

Other

dependencies: Autobump fiatVersion ( 02c72b04 )
dependencies: Autobump korkVersion ( 4ee39086 )

Kayenta 2.38.1

Other

dependencies: Autobump orcaVersion ( d6f5f132 )
dependencies: Autobump orcaVersion ( a08492ac )

Orca 8.36.2

Features

jenkins: Enable Jenkins job triggers for jobs in sub-folders (#4618) ( a5d81577 )
jenkins: Enable Jenkins job triggers for jobs in sub-folders ( a5d81577 )
jenkins: initiate flag to false in tests ( a5d81577 )

Fixes

jenkins: Enable properties and artifacts with job name as query parameter (#4661) ( df6e058b )
jenkins: Enable properties and artifacts with job name as query parameter ( df6e058b )
jenkins: Enable properties and artifacts with job name as query parameter ( df6e058b )

Other

dependencies: Autobump fiatVersion ( 73d47cca )
dependencies: Autobump korkVersion ( 3d2eb9f0 )

Rosco 1.18.2

Other

dependencies: Autobump korkVersion ( d00efe25 )

Spinnaker Release 1.28.8

Fri, 02 Feb 2024 03:36:25 +0000

Clouddriver 5.76.7

Features

feat: Add the possibility to update the default handler for the Global Resource Property Registry. (#5963) ( da2179c4 )
gcp: provide a configurable option to bypass gcp account health check. (backport #6093) ( 02b021ee )
gcp: provide a configurable option to bypass gcp account health check. ( 02b021ee )
gcp: provide a configurable option to bypass gcp account health check. ( 02b021ee )
gcp: replace with in-line check solution. ( 02b021ee )

Fixes

builds: Backport flag for installing aws cli ( 3180485c )
gcp: Fix Google Health indicator tests ( 02b021ee )

Other

dependencies: Autobump fiatVersion ( 860f4a4a )
dependencies: Autobump korkVersion ( d0b06758 )

Deck 3.9.5

Features

feat: Add feature flag for multi block failure messages. (backport #10061) ( 0d188f1d )
feat: Split deployment failure messages. (#10060) ( 43436ee1 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions (#10036) ( e51a58bc )

Fixes

fix: Scaling bounds should parse float not int (#10026) ( d8e2597b )

Echo 2.34.7

Fixes

gha: Fix github status log and add tests (#1316) ( 4f2b91c3 )
gha: Fix github status log and add tests ( 4f2b91c3 )

Other

dependencies: Autobump fiatVersion ( f004199d )
dependencies: Autobump korkVersion ( f5afc571 )
language: Update test message to be better ( 4f2b91c3 )

Fiat 1.31.6

Other

dependencies: Autobump korkVersion ( b6ca385e )

Front50 2.25.6

Other

dependencies: Autobump fiatVersion ( f48b13a3 )
dependencies: Autobump korkVersion ( 7827a298 )

Gate 6.55.6

Fixes

cachingFilter: Allow disabling the content caching filter (#1699: ( e3e44627 )

Other

dependencies: Autobump fiatVersion ( d2bd7c06 )
dependencies: Autobump korkVersion ( 52ccc697 )

Igor 4.7.6

Other

dependencies: Autobump fiatVersion ( 2a5a527c )
dependencies: Autobump korkVersion ( 8010a917 )

Kayenta 2.32.7

Other

dependencies: Autobump orcaVersion ( 6b092eaa )

Orca 8.24.8

Features

fix: duplicate entry exception for correlation_ids table. (#4521) ( 14fd03c1 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions (#4546) ( 735ae07e )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 735ae07e )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 735ae07e )

Fixes

front50: teach MonitorPipelineTask to handle missing/null execution ids (#4555) ( a65d34f9 )

Other

dependencies: Autobump fiatVersion ( 0bf1cb4c )
dependencies: Autobump korkVersion ( 6e3a995f )

Rosco 1.8.7

Features

helm/bake: Add additional input fields where we can fill in details of the APIs versions (backport #1020) ( e8bf6c58 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( e8bf6c58 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( e8bf6c58 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( e8bf6c58 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( e8bf6c58 )
helm/bake: Fix back-port into release 1.28.x ( e8bf6c58 )

Other

dependencies: Autobump korkVersion ( 2e32ff66 )
feature: Change codeql to scan daily instead of weekly ( e8bf6c58 )

Spinnaker Release 1.33.0

Fri, 05 Jan 2024 06:01:54 +0000

Changelog

Note: Broken Functionality

Spinnaker 1.33.0 upgrades to liquibase 4.24.0 which breaks the following scenarios when using postgres:

new installation with versions 1.33.0, 1.33.1, 1.34.0 & 1.34.1
upgrade/migration from versions < 1.33.0 to 1.33.0/1.33.1/1.33.2/1.34.0/1.34.1/1.34.2

These scenarios work from Spinnaker 1.33.3 (and above) and Spinnaker 1.34.3 (and above).

See https://github.com/spinnaker/spinnaker/issues/6941 and https://github.com/spinnaker/spinnaker/issues/6942 for more details.

Note: This release requires Halyard version 1.45.0 or later.

Spinnaker Release 1.30.6

Thu, 07 Dec 2023 21:00:25 +0000

Clouddriver 5.80.9

Features

gcp: provide a configurable option to bypass gcp account health check. (backport #6093) ( ef4bbdc4 )
gcp: provide a configurable option to bypass gcp account health check. ( ef4bbdc4 )
gcp: replace with in-line check solution. ( ef4bbdc4 )

Kayenta 2.36.5

Other

dependencies: Autobump orcaVersion ( b5bd22c5 )

Spinnaker Release 1.32.3

Tue, 28 Nov 2023 10:25:22 +0000

Clouddriver 5.82.1

Fixes

fix: Fix docker build in GHA by removing some of the GHA tools (#6033) ( ed1cc7f5 )
cats: passing incorrect redis config into interval provider (#6105) ( 51475a14 )
lambda: Lambda is leaking threads on agent refreshes. remove the custom threadpool (#6048) ( 49050ee1 )

Deck 3.15.2

Features

helm/bake: Add additional input fields where we can fill in details of the APIs versions (#10036) ( 5ef9c103 )

Fixes

fix: Scaling bounds should parse float not int (#10026) ( f788525d )
kubernetes: export rollout restart stage so it’s actually available for use (#10037) ( 028ca72b )
lambda: available Runtimes shared between Deploy stage and Functions tab (#10050) ( 18138469 )

Orca 8.36.1

Features

fix: duplicate entry exception for correlation_ids table. (#4521) ( da001957 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions (#4546) ( 859f1f27 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 859f1f27 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 859f1f27 )

Fixes

artifacts: Automated triggers with artifact constraints are broken if you have 2 or more of the same type (backport #4579) ( 83c37a30 )
artifacts: Automated triggers with artifact constraints are broken if you have 2 or more of the same type ( 83c37a30 )
artifacts: resolving git conflicts from #4579 for release-1.32.x ( 83c37a30 )
artifacts: Parent and child pipeline artifact resolution (backport #4575) ( c0fd7a87 )
front50: teach MonitorPipelineTask to handle missing/null execution ids (#4555) ( b15787fa )
vpc: add data annotation to vpc (#4534) ( 663057c9 )

Rosco 1.18.1

Features

helm/bake: Add additional input fields where we can fill in details of the APIs versions (#1020) ( 93ae1b49 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 93ae1b49 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 93ae1b49 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 93ae1b49 )

Other

feature: Change codeql to scan daily instead of weekly ( 93ae1b49 )

Spinnaker Release 1.31.3

Tue, 28 Nov 2023 08:10:46 +0000

Clouddriver 5.81.2

Fixes

fix: Fix docker build in GHA by removing some of the GHA tools (#6033) ( 3cde031c )
cats: passing incorrect redis config into interval provider (#6105) ( 05ecbef9 )
lambda: Lambda is leaking threads on agent refreshes. remove the custom threadpool (#6048) ( e1de7042 )

Deck 3.14.2

Features

helm/bake: Add additional input fields where we can fill in details of the APIs versions (#10036) ( c0c1f529 )

Fixes

fix: Updating Lambda functions available Runtimes ( 669d1ede )
fix: Scaling bounds should parse float not int (#10026) ( 69db5b34 )

Orca 8.33.2

Features

fix: duplicate entry exception for correlation_ids table. (#4521) ( e7e0c1bc )
helm/bake: Add additional input fields where we can fill in details of the APIs versions (#4546) ( 3510866c )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 3510866c )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 3510866c )

Fixes

artifacts: Automated triggers with artifact constraints are broken if you have 2 or more of the same type (backport #4579) ( 91de7c3b )
artifacts: Automated triggers with artifact constraints are broken if you have 2 or more of the same type ( 91de7c3b )
artifacts: resolving git conflicts from #4579 for release-1.31.x ( 91de7c3b )
artifacts: Parent and child pipeline artifact resolution (backport #4575) ( 6ad5cd01 )
front50: teach MonitorPipelineTask to handle missing/null execution ids (#4555) ( eccc5c07 )
vpc: add data annotation to vpc (#4534) ( 20221342 )

Other

artifacts: partially reverting #4397 ( 91de7c3b )
artifacts: reverted #4489 ( 91de7c3b )
artifacts: reverted #4526 ( 91de7c3b )
artifacts: added test when parent pipeline does not provide expected artifacts ( 91de7c3b )
artifacts: resolve artifacts for default and prior artifacts ( 91de7c3b )

Rosco 1.17.2

Features

helm/bake: Add additional input fields where we can fill in details of the APIs versions (#1020) ( 6a866e7c )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 6a866e7c )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 6a866e7c )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 6a866e7c )

Other

feature: Change codeql to scan daily instead of weekly ( 6a866e7c )

Spinnaker Release 1.30.5

Tue, 28 Nov 2023 08:04:27 +0000

Clouddriver 5.80.8

Features

lambda: Lambda calls default timeout after 50 seconds causing longer running lambdas to fail. This adds configurable timeouts for lambda invocations (#6041) ( 2bb089d6 )

Fixes

cats: passing incorrect redis config into interval provider (#6105) ( 75e00c7a )
lambda: Lambda is leaking threads on agent refreshes. remove the custom threadpool (#6048) ( c5109598 )

Deck 3.13.3

Features

helm/bake: Add additional input fields where we can fill in details of the APIs versions (#10036) ( e9358ab5 )

Fixes

fix: Updating Lambda functions available Runtimes (#10055) ( 25e472ea )
fix: Scaling bounds should parse float not int (#10026) ( f8dc0af0 )

Front50 2.28.5

Fixes

dependency: fix dependency version leak of google-api-services-storage from kork in front50-web (#1302) ( 66d8f009 )

Orca 8.31.6

Features

fix: duplicate entry exception for correlation_ids table. (#4521) ( a4404a6a )
helm/bake: Add additional input fields where we can fill in details of the APIs versions (#4546) ( d0b21e32 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( d0b21e32 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( d0b21e32 )

Fixes

artifacts: Automated triggers with artifact constraints are broken if you have 2 or more of the same type (backport #4579) ( 4740c167 )
artifacts: Automated triggers with artifact constraints are broken if you have 2 or more of the same type ( 4740c167 )
artifacts: resolving git conflicts from #4579 for release-1.30.x ( 4740c167 )
artifacts: Parent and child pipeline artifact resolution (backport #4575) ( 1fc563b1 )
front50: teach MonitorPipelineTask to handle missing/null execution ids (#4555) ( 5ad5cce6 )
vpc: add data annotation to vpc (#4534) ( ff5d2cf9 )

Rosco 1.13.4

Features

helm/bake: Add additional input fields where we can fill in details of the APIs versions (#1020) ( 5dba8f11 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 5dba8f11 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 5dba8f11 )
helm/bake: Add additional input fields where we can fill in details of the APIs versions ( 5dba8f11 )

Other

feature: Change codeql to scan daily instead of weekly ( 5dba8f11 )

Spinnaker Release 1.32.2

Wed, 20 Sep 2023 20:57:07 +0000

Igor 4.13.3

Fixes

java17: stop accessing private fields, run tests using JRE17 (#1173) ( 95c19bd7 )
java17: add Jackson converter to RestAdapters to avoid Gson (#1174) ( 786143df )

Spinnaker Release 1.32.1

Mon, 18 Sep 2023 17:35:21 +0000

Igor 4.13.1

Fixes

java17: remove long-deprecated import that doesn’t work with JRE17 (#1170) ( 0e308270 )

Spinnaker Release 1.30.4

Fri, 08 Sep 2023 21:15:24 +0000

Clouddriver 5.80.7

Fixes

fix: Fix docker build in GHA by removing some of the GHA tools (#6033) ( c6dbf249 )
builds: Backport flag for installing aws cli ( 6f7a522c )

Other

dependencies: Autobump fiatVersion ( 2ca3cb32 )
dependencies: Autobump fiatVersion ( 2cdfe2ec )
dependencies: Autobump korkVersion ( a39a9bd3 )
deps: bump docker/build-push-action from 3 to 4 (#5927) ( a039548c )
deps: bump actions/setup-java from 2 to 3 (#5928) ( 838dba0b )
deps: bump actions/checkout from 2 to 3 (#5924) ( 765eed3e )
deps: bump actions/cache from 2 to 3 (#5926) ( 6261e528 )
gha: replace deprecated set-output commands with environment files (#5930) ( 399310db )
gha: replace action for creating github releases (backport #5929) ( e5652896 )
gha: replace action for creating github releases ( e5652896 )
gha: resolve conflicts ( e5652896 )
gha: update to docker/login-action@v2 to stay up to date (#5920) ( ec64a4ab )

Deck 3.13.2

Other

Revert “fix(core): conditionally hide expression evaluation warning messages (#9771)” (#10021) ( c66d5423 )

Echo 2.37.3

Other

dependencies: Autobump fiatVersion ( efecf203 )
dependencies: Autobump fiatVersion ( 3ad7e607 )
dependencies: Autobump korkVersion ( 3b007a49 )

Fiat 1.37.4

Fixes

ssl: Removed unused deprecated okHttpClientConfig from retrofitConfig. (#1082) ( 6f40a11f )

Other

dependencies: Autobump korkVersion ( 80b6e407 )

Front50 2.28.4

Other

dependencies: Autobump fiatVersion ( 423c8b80 )
dependencies: Autobump fiatVersion ( 9a606e21 )
dependencies: Autobump korkVersion ( c32e2dd4 )

Gate 6.58.3

Fixes

cachingFilter: Allow disabling the content caching filter (#1699: ( 9bb15d00 )

Other

dependencies: Autobump fiatVersion ( 59227922 )
dependencies: Autobump fiatVersion ( 4fa3335a )
dependencies: Autobump korkVersion ( 25de9d2c )

Igor 4.11.3

Other

dependencies: Autobump fiatVersion ( 4349ba15 )
dependencies: Autobump fiatVersion ( 343c062b )
dependencies: Autobump korkVersion ( ce2a4ce0 )

Kayenta 2.36.4

Fixes

orca: Fix orca contributors status. (backport #977) ( 00a3c334 )

Other

dependencies: Autobump orcaVersion ( d53ccd7e )
dependencies: Autobump orcaVersion ( 5b781577 )

Orca 8.31.5

Other

dependencies: Autobump fiatVersion ( d7bc9ecc )
dependencies: Autobump fiatVersion ( c329397c )
dependencies: Autobump korkVersion ( 1e7ce3e0 )

Rosco 1.13.3

Other

dependencies: Autobump korkVersion ( 2f2b7ffa )

Spinnaker Release 1.29.7

Fri, 08 Sep 2023 19:19:56 +0000

Clouddriver 5.78.13

Fixes

fix: Fix docker build in GHA by removing some of the GHA tools (#6033) ( 172d6795 )
builds: Backport flag for installing aws cli ( beb61a41 )

Other

dependencies: Autobump fiatVersion ( 9583896f )
deps: bump docker/build-push-action from 3 to 4 (#5927) ( 81738eac )
deps: bump actions/setup-java from 2 to 3 (#5928) ( 0e555c28 )
deps: bump actions/checkout from 2 to 3 (#5924) ( 105974b4 )
deps: bump actions/cache from 2 to 3 (#5926) ( 11ecac5d )
gha: replace deprecated set-output commands with environment files (#5930) ( 4056d9e2 )
gha: replace action for creating github releases (backport #5929) ( a9291583 )
gha: replace action for creating github releases ( a9291583 )
gha: resolve conflicts ( a9291583 )
gha: update to docker/login-action@v2 to stay up to date (#5920) ( 4bc7cea0 )

Deck 3.12.4

Other

Revert “fix(core): conditionally hide expression evaluation warning messages (#9771)” (#10021) ( 4bdf3816 )

Echo 2.36.5

Other

dependencies: Autobump fiatVersion ( 18475d73 )

Fiat 1.36.5

Fixes

ssl: Removed unused deprecated okHttpClientConfig from retrofitConfig. (#1082) ( a8924d97 )

Front50 2.27.5

Other

dependencies: Autobump fiatVersion ( 53034d71 )

Gate 6.57.5

Fixes

cachingFilter: Allow disabling the content caching filter (#1699: ( f4464f77 )

Other

dependencies: Autobump fiatVersion ( 33b33d92 )

Igor 4.10.5

Other

dependencies: Autobump fiatVersion ( ec1d009c )

Kayenta 2.35.6

Other

dependencies: Autobump orcaVersion ( 6820a895 )

Orca 8.27.6

Other

dependencies: Autobump fiatVersion ( 63e80604 )

Spinnaker Release 1.32.0

Fri, 08 Sep 2023 18:04:13 +0000

Changelog

Note: This release requires Halyard version 1.62.0 or later.

Java 17

Front50 and Igor containers now default to running with the Java 17 JRE. In an upcoming release (likely 1.33) all other services will default to the Java 17 JRE. If you encounter issues with these containers you can opt-out and use the Java 11 JRE containers. Users of Halyard can do this by specying imageVariant: JAVA11 or imageVariant: UBUNTU_JAVA11 in their halconfig.

Spinnaker Release 1.31.2

Fri, 08 Sep 2023 17:51:07 +0000

Deck 3.14.1

Other

Revert “fix(core): conditionally hide expression evaluation warning messages (#9771)” (#10021) ( 734c8959 )

Front50 2.29.2

Fixes

dependency: fix dependency version leak of google-api-services-storage from kork in front50-web (#1302) ( f0494570 )

Gate 6.59.2

Fixes

cachingFilter: Allow disabling the content caching filter (#1699: ( 7bc7898b )

Spinnaker Release 1.31.1

Tue, 29 Aug 2023 18:39:54 +0000

Clouddriver 5.81.1

Fixes

builds: Backport flag for installing aws cli ( 5116a2e4 )
gce: remove the duplicate cache attribute “subnet” and update the test (#5977) ( 40ee2453 )

Other

dependencies: Autobump fiatVersion ( 3f4607bc )
dependencies: Autobump korkVersion ( fe57848d )

Echo 2.38.1

Fixes

gha: Fix github status log and add tests (#1316) ( 3df5271a )
gha: Fix github status log and add tests ( 3df5271a )

Other

dependencies: Autobump fiatVersion ( d20da255 )
dependencies: Autobump korkVersion ( a157fc69 )
language: Update test message to be better ( 3df5271a )

Fiat 1.41.1

Fixes

roles-sync: fix CallableCache’s NPE exception for caching synchronization strategy (#1077) ( c876f39e )
roles-sync: fix callable cache NPE exception for caching synchronization strategy ( c876f39e )
roles-sync: added tests ( c876f39e )
ssl: Removed unused deprecated okHttpClientConfig from retrofitConfig. (#1082) ( a74ce838 )

Other

dependencies: Autobump korkVersion ( c065b481 )

Front50 2.29.1

Fixes

core: skip existing items with null ids in StorageServiceSupport.fetchAllItemsOptimized (#1279) ( 4fb2bdda )
core: tolerate items with null ids (#1276) ( 765d822c )
core: filter out items with null ids in StorageServiceSupport.fetchAllItems ( 765d822c )
core: tolerate items with null ids in StorageServiceSupport.findById ( 765d822c )
core: filter out items with null ids in StorageServiceSupport.fetchAllItemsOptimized ( 765d822c )
core: throw an IllegalArgumentException from StorageServiceSupport.update ( 765d822c )
web: check trigger.getType() for null before invoking equals method (#1277) ( 54cc672b )

Other

core: demonstrate current behavior with a pipeline with a null id in the database ( 765d822c )
core: demonstrate behavior of StorageServiceSupport.bulkImport of a pipeline with a null id ( 765d822c )
core/test: combine null id tests in PipelineControllerTck ( 765d822c )
dependencies: Autobump fiatVersion ( 3909af74 )
dependencies: Autobump korkVersion ( 026a2007 )

Gate 6.59.1

Other

dependencies: Autobump fiatVersion ( e83ce5be )
dependencies: Autobump korkVersion ( 552715b6 )

Igor 4.12.1

Other

dependencies: Autobump fiatVersion ( 3fb141e6 )
dependencies: Autobump korkVersion ( 3879289e )

Kayenta 2.37.1

Fixes

orca: Fix orca contributors status. (backport #977) ( 1d2b6789 )

Other

dependencies: Autobump orcaVersion ( 6c73ba3c )

Orca 8.33.1

Fixes

artifacts: consider requiredArtifactIds in expected artifacts when trigger is pipeline type (#4489) ( ed4d2d49 )
queue: fix ability to cancel a zombied execution (#4473) ( 27820937 )
queue: fix ability to cancel a zombied execution ( 27820937 )
queue: undo unintentional change ( 27820937 )
queue: add more logging ( 27820937 )

Other

dependencies: Autobump fiatVersion ( c68cc87d )
dependencies: Autobump korkVersion ( 625d411e )

Rosco 1.17.1

Other

dependencies: Autobump korkVersion ( 4ec52a45 )

Spinnaker Release 1.30.3

Fri, 18 Aug 2023 00:46:32 +0000

Clouddriver 5.80.4

Features

feat: Add the possibility to update the default handler for the Global Resource Property Registry. (#5963) ( 8157baf5 )

Fixes

gce: remove the duplicate cache attribute “subnet” and update the test (#5977) ( e764d77d )

Other

dependencies: Autobump fiatVersion ( 99db58a4 )
dependencies: Autobump korkVersion ( b02f7047 )

Deck 3.13.1

Features

deck: make StageFailureMessage component overridable (backport #9994) ( 4ad1f067 )
deck: make StageFailureMessage component overridable ( 4ad1f067 )

Other

build: fix backport merge conflict ( 4ad1f067 )

Echo 2.37.2

Fixes

gha: Fix github status log and add tests (#1316) ( 2faf498c )
gha: Fix github status log and add tests ( 2faf498c )

Other

dependencies: Autobump fiatVersion ( 2d1b3e4a )
dependencies: Autobump korkVersion ( ad67da3b )
language: Update test message to be better ( 2faf498c )

Fiat 1.37.2

Fixes

roles-sync: fix CallableCache’s NPE exception for caching synchronization strategy (#1077) ( cd168217 )
roles-sync: fix callable cache NPE exception for caching synchronization strategy ( cd168217 )
roles-sync: added tests ( cd168217 )

Other

dependencies: Autobump korkVersion ( d0edc68b )

Front50 2.28.3

Other

dependencies: Autobump fiatVersion ( 06c640b1 )
dependencies: Autobump korkVersion ( 5742c8f7 )

Gate 6.58.2

Other

dependencies: Autobump fiatVersion ( 0c614f8a )
dependencies: Autobump korkVersion ( fdef09a0 )

Igor 4.11.2

Other

dependencies: Autobump fiatVersion ( 65a7c282 )
dependencies: Autobump korkVersion ( 18d516ae )

Kayenta 2.36.3

Other

dependencies: Autobump orcaVersion ( 91ea710a )

Orca 8.31.3

Fixes

artifacts: consider requiredArtifactIds in expected artifacts when trigger is pipeline type (#4489) ( 977d164e )
queue: fix ability to cancel a zombied execution (#4473) ( 2ff457f0 )
queue: fix ability to cancel a zombied execution ( 2ff457f0 )
queue: undo unintentional change ( 2ff457f0 )
queue: add more logging ( 2ff457f0 )
queue: Manual Judgment propagation ( ba9ac0d6 )
waiting-executions: concurrent waiting executions doesn’t follow FIFO (backport #4415) ( c8a1745f )

Other

dependencies: Autobump fiatVersion ( fe1eda71 )
dependencies: Autobump korkVersion ( 58fedce4 )

Rosco 1.13.2

Other

dependencies: Autobump korkVersion ( e99825cc )

Spinnaker Release 1.29.6

Fri, 18 Aug 2023 00:34:53 +0000

Clouddriver 5.78.7

Features

feat: Add the possibility to update the default handler for the Global Resource Property Registry. (#5963) ( 2ae5fb9a )

Fixes

gce: remove the duplicate cache attribute “subnet” and update the test (#5977) ( 010b360b )

Other

dependencies: Autobump fiatVersion ( d6b93e09 )
dependencies: Autobump korkVersion ( 00f81d6a )

Echo 2.36.4

Fixes

gha: Fix github status log and add tests (#1316) ( dbb22810 )
gha: Fix github status log and add tests ( dbb22810 )

Other

dependencies: Autobump fiatVersion ( 577979e5 )
dependencies: Autobump korkVersion ( d6cfbca1 )
language: Update test message to be better ( dbb22810 )

Fiat 1.36.4

Fixes

roles-sync: fix CallableCache’s NPE exception for caching synchronization strategy (#1077) ( 4aac1ef8 )
roles-sync: fix callable cache NPE exception for caching synchronization strategy ( 4aac1ef8 )
roles-sync: added tests ( 4aac1ef8 )

Other

dependencies: Autobump korkVersion ( 78cadf60 )

Front50 2.27.4

Other

dependencies: Autobump fiatVersion ( 06b08aed )
dependencies: Autobump korkVersion ( 7f503e7a )

Gate 6.57.4

Other

dependencies: Autobump fiatVersion ( 0d9c4d62 )
dependencies: Autobump korkVersion ( 648126d7 )

Igor 4.10.4

Other

dependencies: Autobump fiatVersion ( 2cfb13ec )
dependencies: Autobump korkVersion ( 6bc03dbe )

Kayenta 2.35.5

Other

dependencies: Autobump orcaVersion ( b4e9bb86 )

Orca 8.27.5

Fixes

queue: Manual Judgment propagation ( 3e798201 )

Other

dependencies: Autobump fiatVersion ( 06ec03eb )
dependencies: Autobump korkVersion ( a3baf6df )

Rosco 1.12.4

Other

dependencies: Autobump korkVersion ( 3dc64a66 )

Spinnaker Release 1.31.0

Wed, 21 Jun 2023 06:22:09 +0000

Changelog

Note: This release requires Halyard version 1.45.0 or later.

Spring Boot 2.5

As part of the modernization effort, we’ve continued to upgrade Spring Boot. Spinnaker 1.31.0 now uses Spring Boot 2.5.14, an upgrade from Spinnaker 1.30.0’s use of Spring Boot 2.4.13.

Spinnaker Release 1.30.2

Thu, 01 Jun 2023 08:14:51 +0000

Clouddriver 5.80.2

Fixes

aws: ECS Service Tagging broken (backport #5954) ( 39ff8112 )

Front50 2.28.2

Fixes

migrations: do not migrate redblack pipelines without stages (#1259) ( 9aa1a7dc )
validator: Fix NPE when traffic management is not defined in a deployment manifest (#1253) ( 4657feec )

Kayenta 2.36.2

Fixes

signalfx: Fixed metric type missing due to duplicated field from parent class (#957) ( d2a4c791 )

Other

dependencies: Autobump orcaVersion ( 2583bbf4 )

Orca 8.31.2

Fixes

deployment: fixed missing namespace while fetching manifest details from clouddriver (#4453) ( 7a0b18d3 )

Spinnaker Release 1.29.5

Thu, 01 Jun 2023 08:10:08 +0000

Clouddriver 5.78.6

Fixes

aws: ECS Service Tagging broken (backport #5954) ( e88dfab1 )
metrics: revert metric names to pre-Java (#5936) ( 6dccbba0 )
metrics: revert metric names to pre-Java closing spinnaker/spinnaker#6821 ( 6dccbba0 )
metrics: remove unused extension ( 6dccbba0 )

Deck 3.12.3

Fixes

fix: UI crashes when running pipeline(s) with many stages. (backport #9960) ( 3e0f88f0 )

Kayenta 2.35.4

Other

dependencies: Autobump orcaVersion ( 1f1f73d8 )

Orca 8.27.4

Fixes

deployment: fixed missing namespace while fetching manifest details from clouddriver (#4453) ( 6ca6d712 )

Spinnaker Release 1.28.7

Thu, 01 Jun 2023 08:05:43 +0000

Clouddriver 5.76.6

Fixes

aws: ECS Service Tagging broken (backport #5954) ( 8a7993eb )

Deck 3.9.4

Fixes

fix: UI crashes when running pipeline(s) with many stages. (backport #9960) ( c43b1057 )
aws: Fixing bugs related to clone CX when instance types are incompatible with image/region (backport #9901) ( ccd39595 )
aws: Fixing bugs related to clone CX when instance types are incompatible with image/region ( ccd39595 )
core: apps always display as unconfigured (#9853) ( 44b80f38 )

Kayenta 2.32.6

Other

dependencies: Autobump orcaVersion ( 48db746d )

Orca 8.24.7

Fixes

deployment: fixed missing namespace while fetching manifest details from clouddriver (#4453) ( cd4e9ab5 )

Spinnaker Release 1.27.6

Thu, 01 Jun 2023 07:57:25 +0000

Clouddriver 5.74.8

Fixes

aws: ECS Service Tagging broken (backport #5954) ( 8fc7f9bb )

Kayenta 2.31.7

Other

dependencies: Autobump orcaVersion ( 34d94f22 )

Orca 8.18.11

Fixes

blue-green-deploy: removing old failed manifests ( 4d53e3af )
blue-green-deploy: refactoring ( 4d53e3af )
blue-green-deploy: refactoring ( 4d53e3af )
blue-green-deploy: added docs ( 4d53e3af )
blue-green-deploy: added test to validate new behaviour ( 4d53e3af )

Other

conflict: resolved conflicts ( 4d53e3af )

Spinnaker Release 1.30.1

Fri, 07 Apr 2023 03:46:41 +0000

Changelog

SAML

Fixed an issue with SAML integration that was introduced in 1.30.0

Clouddriver 5.80.1

Fixes

metrics: revert metric names to pre-Java (#5936) ( 7758866b )
metrics: revert metric names to pre-Java closing spinnaker/spinnaker#6821 ( 7758866b )
metrics: remove unused extension ( 7758866b )

Other

dependencies: Autobump fiatVersion ( b2919632 )
dependencies: don’t create an autobump PR for halyard on a clouddriver release branch (#5677) ( a6693305 )
dependencies: Autobump korkVersion ( ea05ae18 )

Echo 2.37.1

Other

dependencies: Autobump fiatVersion ( 43d43638 )
dependencies: Autobump korkVersion ( a3a6cdd3 )

Fiat 1.37.1

Other

dependencies: Autobump korkVersion ( 8bf74c28 )

Front50 2.28.1

Other

dependencies: Autobump fiatVersion ( 1991a992 )
dependencies: don’t create an autobump PR for halyard on a front50 release branch (#1115) ( 523d64b3 )
dependencies: Autobump korkVersion ( 90d8d730 )

Gate 6.58.1

Other

dependencies: Autobump fiatVersion ( f6408bd5 )
dependencies: Autobump korkVersion ( 77b3df0d )

Igor 4.11.1

Other

dependencies: Autobump fiatVersion ( d77263d8 )
dependencies: Autobump korkVersion ( 9de200a8 )

Kayenta 2.36.1

Other

dependencies: Autobump orcaVersion ( bc7e3bf0 )

Orca 8.31.1

Other

dependencies: Autobump korkVersion (#4444) ( 283c5051 )
dependencies: Autobump korkVersion ( f84c42dd )

Rosco 1.13.1

Other

dependencies: Autobump korkVersion ( 10fa720a )

Spinnaker Release 1.29.4

Tue, 28 Mar 2023 23:22:30 +0000

Clouddriver 5.78.5

Fixes

core: Renamed a query parameter for template tags (#5906) ( 3c189489 )
ecr: Two credentials with same accountId confuses EcrImageProvider with different regions (#5885) ( e998b05c )
test: Make the regions reasonable here too ( e998b05c )

Other

aws: Update AWS IAM Authenticator version ( d1176b3c )
dependencies: Autobump fiatVersion ( 08bcf698 )

Echo 2.36.3

Other

dependencies: Autobump fiatVersion ( 8e03a0af )

Fiat 1.36.3

Fixes

logs: Redacted secret data in logs. (#1029) ( 51fa0be1 )
logs: Redacted secret data in logs. ( 51fa0be1 )
logs: Redacted secret data in logs. ( 51fa0be1 )
logs: Redacted secret data in logs. ( 51fa0be1 )
logs: Redacted secret data in logs. ( 51fa0be1 )
logs: Redacted secret data in logs. ( 51fa0be1 )

Front50 2.27.3

Fixes

cache: Fix caching all pipelines during sync loop. ( efff3fb7 )
cache: Fix caching all pipelines drring sync loop. ( efff3fb7 )
sql: Populating lastModified field for pipelines when loading objects. (#1220) ( efff3fb7 )

Other

dependencies: Autobump fiatVersion ( ad7e39ea )

Gate 6.57.3

Other

dependencies: Autobump fiatVersion ( 6e33b5a2 )

Igor 4.10.3

Other

dependencies: Autobump fiatVersion ( fc745872 )

Kayenta 2.35.3

Other

dependencies: Autobump orcaVersion ( 297f6a95 )

Orca 8.27.3

Fixes

blue-green-deploy: removing old failed manifests ( ccdbea7e )
blue-green-deploy: refactoring ( ccdbea7e )
blue-green-deploy: refactoring ( ccdbea7e )
blue-green-deploy: added docs ( ccdbea7e )
blue-green-deploy: added test to validate new behaviour ( ccdbea7e )

Other

conflict: resolved conflicts ( ccdbea7e )
dependencies: Autobump fiatVersion ( bb38bc6d )

Spinnaker Release 1.28.6

Tue, 28 Mar 2023 20:37:41 +0000

Clouddriver 5.76.5

Fixes

core: Renamed a query parameter for template tags (#5906) ( 42df94e7 )

Other

aws: Update AWS IAM Authenticator version ( 4d04f26c )
dependencies: Autobump fiatVersion ( a84dfe90 )

Echo 2.34.6

Other

dependencies: Autobump fiatVersion ( 0957fef9 )

Fiat 1.31.5

Fixes

logs: Redacted secret data in logs. (#1029) ( 9beee951 )
logs: Redacted secret data in logs. ( 9beee951 )
logs: Redacted secret data in logs. ( 9beee951 )
logs: Redacted secret data in logs. ( 9beee951 )
logs: Redacted secret data in logs. ( 9beee951 )
logs: Redacted secret data in logs. ( 9beee951 )

Front50 2.25.5

Fixes

cache: Fix caching all pipelines during sync loop. ( 22c2a6d6 )
cache: Fix caching all pipelines drring sync loop. ( 22c2a6d6 )
sql: Populating lastModified field for pipelines when loading objects. (#1220) ( 22c2a6d6 )

Other

dependencies: Autobump fiatVersion ( c4721267 )

Gate 6.55.5

Other

dependencies: Autobump fiatVersion ( 228b57f7 )

Igor 4.7.5

Other

dependencies: Autobump fiatVersion ( ac7fa51e )

Kayenta 2.32.5

Other

dependencies: Autobump orcaVersion ( e4bae4ed )

Orca 8.24.6

Fixes

blue-green-deploy: removing old failed manifests ( 7a36cb82 )
blue-green-deploy: refactoring ( 7a36cb82 )
blue-green-deploy: refactoring ( 7a36cb82 )
blue-green-deploy: added docs ( 7a36cb82 )
blue-green-deploy: added test to validate new behaviour ( 7a36cb82 )

Other

conflict: resolved conflicts ( 7a36cb82 )
dependencies: Autobump fiatVersion ( 3ae522b7 )

Spinnaker Release 1.30.0

Tue, 28 Mar 2023 00:26:28 +0000

Changelog

Note: This release requires Halyard version 1.45.0 or later.

Spring Boot 2.4

Spinnaker 1.30 uses Spring Boot 2.4, where 1.29 uses Spring Boot 2.3. Spring Boot 2.4 considers session data cached by Spring Boot 2.3 invalid. Therefore, users with cached sessions will be unable to log in until the invalid information is removed from the cache. Open browser windows to Spinnaker are unresponsive after the deployment until they’re reloaded. Executing:

Spinnaker Release 1.27.5

Mon, 27 Mar 2023 18:16:51 +0000

Clouddriver 5.74.7

Fixes

core: Renamed a query parameter for template tags (#5906) ( 29460a33 )

Other

dependencies: Autobump fiatVersion ( 968882e8 )

Echo 2.32.7

Other

dependencies: Autobump fiatVersion ( 296822a0 )

Fiat 1.28.13

Fixes

logs: Redacted secret data in logs. (#1029) ( 19e4ef2d )
logs: Redacted secret data in logs. ( 19e4ef2d )
logs: Redacted secret data in logs. ( 19e4ef2d )
logs: Redacted secret data in logs. ( 19e4ef2d )
logs: Redacted secret data in logs. ( 19e4ef2d )
logs: Redacted secret data in logs. ( 19e4ef2d )

Front50 2.23.10

Fixes

cache: Fix caching all pipelines during sync loop. ( 0367e48c )
cache: Fix caching all pipelines drring sync loop. ( 0367e48c )
sql: Populating lastModified field for pipelines when loading objects. (#1220) ( 0367e48c )

Other

dependencies: Autobump fiatVersion ( f5db63c1 )

Gate 6.54.8

Other

dependencies: Autobump fiatVersion ( 0623f2a7 )

Igor 4.6.8

Other

dependencies: Autobump fiatVersion ( 2bb53738 )

Kayenta 2.31.6

Other

dependencies: Autobump orcaVersion ( 67a0efba )

Orca 8.18.10

Other

dependencies: Autobump fiatVersion ( 8bb96793 )

Spinnaker Release 1.29.3

Tue, 07 Mar 2023 16:37:28 +0000

Clouddriver 5.78.4

Features

gke: Enables gcloud auth plugin for 1.26+ GKE clusters (#5847) ( 31e8fc3f )
gke: Enables gcloud auth plugin for 1.26+ GKE clusters ( 31e8fc3f )
gke: Bump google cloud sdk and add the plugin for GKE 1.26+ ( 31e8fc3f )

Fixes

gce: fixed the error caused by account removal (#5882) ( 61a57c42 )
google: make AbstractAtomicOperationsCredentialsConverter generic type (#5866) ( 56f13ef8 )
kubernetes: Revert to using the dockerImage Artifact Replacer for cronjobs (#5876) ( 34a37b64 )
kubernetes: revert to using the dockerImage artifact replacer for cronjobs ( 34a37b64 )

Other

dependencies: Autobump fiatVersion ( e14eb01d )
dependencies: Autobump korkVersion ( 727f032e )
dependencies: pin version of com.github.tomakehurst:wiremock (#5845) ( 98522b54 )
kubernetes: add failing test to show that the cronJobDockerImageReplacer doesn’t work for match-name-and-tag artifact binding strategy, but the dockerImageReplacer works ( 34a37b64 )

Deck 3.12.2

Fixes

timeout: Added feature flag for rollback timeout ui input. (backport #9937) ( 394ba177 )
timeout: Added feature flag for rollback timeout ui input. ( 394ba177 )
timeout: Added feature flag for rollback timeout ui input. ( 394ba177 )
timeout: Added feature flag for rollback timeout ui input. ( 394ba177 )
timeout: Added feature flag for rollback timeout ui input. ( 394ba177 )

Echo 2.36.2

Features

event: Add circuit breaker for events sending. (#1233) ( eec8bf55 )
event: Add circuit breaker for events sending. ( eec8bf55 )

Fixes

fix: The circuit breaker feature for sending events to telemetry endpoint is hidden under a required feature flag property (#1241) ( d764c8d3 )

Other

dependencies: Autobump fiatVersion ( 20599741 )
dependencies: Autobump korkVersion ( 4288d345 )

Fiat 1.36.2

Fixes

fix: Should fix the deletion of permissions when resource name is uppercase (#1012) ( 6d9f5050 )

Other

dependencies: Autobump korkVersion ( 7dee734b )

Front50 2.27.2

Other

dependencies: Autobump fiatVersion ( 0ff677e7 )
dependencies: Autobump korkVersion ( 1655d35b )

Gate 6.57.2

Other

dependencies: Autobump fiatVersion ( b779739f )
dependencies: Autobump korkVersion ( 8da31e31 )

Igor 4.10.2

Other

dependencies: Autobump fiatVersion ( ea39d242 )
dependencies: Autobump korkVersion ( 424268b3 )

Kayenta 2.35.2

Other

dependencies: Autobump orcaVersion ( 8294bcb5 )

Orca 8.27.2

Fixes

stageExecution: Extend MJ auth propagate logic for exhaustive cases (#4368) ( 479e034e )
stageExecution: Permission retrieved from last user interaction ( 479e034e )
stageExecution: Include not authenticated to apply backtracking ( 479e034e )
stageExecution: Extended logic for sub cases ( 479e034e )
timeout: Added feature flag for rollback timeout ui input. (backport #4383) ( 50946c24 )
timeout: Added feature flag for rollback timeout ui input. ( 50946c24 )
timeout: Added feature flag for rollback timeout ui input. ( 50946c24 )
timeout: Added feature flag for rollback timeout ui input. ( 50946c24 )
timeout: Added feature flag for rollback timeout ui input. ( 50946c24 )
timeout: Added feature flag for rollback timeout ui input. ( 50946c24 )

Other

dependencies: Autobump fiatVersion ( 80c7ed70 )
dependencies: Autobump korkVersion ( f7e2c2b5 )

Rosco 1.12.3

Other

dependencies: Autobump korkVersion ( 87677651 )

Spinnaker Release 1.28.5

Fri, 03 Mar 2023 17:50:45 +0000

Clouddriver 5.76.4

Features

gke: Enables gcloud auth plugin for 1.26+ GKE clusters (backport #5847) ( 2fa2b60d )
gke: Enables gcloud auth plugin for 1.26+ GKE clusters ( 2fa2b60d )
gke: Enables gcloud auth plugin for 1.26+ GKE clusters ( 2fa2b60d )
gke: Bump google cloud sdk and add the plugin for GKE 1.26+ ( 2fa2b60d )

Fixes

ecr: Two credentials with same accountId confuses EcrImageProvider with different regions (#5885) ( b7a4239b )
kubernetes: Revert to using the dockerImage Artifact Replacer for cronjobs (#5876) ( eb54d18b )
kubernetes: revert to using the dockerImage artifact replacer for cronjobs ( eb54d18b )
permissions: Added evaluator case when fiat is enabled ( 923fa4fb )
permissions: added previous verification to extend sub cases ( 923fa4fb )
permissions: Added evaluator case when fiat is enabled ( 923fa4fb )
style: Added correct code format ( 923fa4fb )
test: Make the regions reasonable here too ( b7a4239b )

Other

dependencies: Autobump fiatVersion ( b0d6a8ef )
dependencies: Autobump korkVersion ( 14e1395a )
dependencies: pin version of com.github.tomakehurst:wiremock (#5845) ( 5d41a38e )
kubernetes: add failing test to show that the cronJobDockerImageReplacer doesn’t work for match-name-and-tag artifact binding strategy, but the dockerImageReplacer works ( eb54d18b )
merge: fix merge conflict in backport ( 2fa2b60d )

Deck 3.9.3

Fixes

timeout: Added feature flag for rollback timeout ui input. (backport #9937) ( 3b8b22aa )
timeout: Added feature flag for rollback timeout ui input. ( 3b8b22aa )
timeout: Added feature flag for rollback timeout ui input. ( 3b8b22aa )
timeout: Added feature flag for rollback timeout ui input. ( 3b8b22aa )
timeout: Added feature flag for rollback timeout ui input. ( 3b8b22aa )

Echo 2.34.5

Features

event: Add circuit breaker for events sending. (#1233) ( 21e965fb )
event: Add circuit breaker for events sending. ( 21e965fb )

Fixes

fix: The circuit breaker feature for sending events to telemetry endpoint is hidden under a required feature flag property (#1241) ( 59bfbecd )

Other

dependencies: Autobump fiatVersion ( 48b04bc2 )
dependencies: Autobump korkVersion ( 4e77a27e )

Fiat 1.31.4

Fixes

fix: Should fix the deletion of permissions when resource name is uppercase (backport #1012) ( 2088171e )

Other

dependencies: Autobump korkVersion ( 30080289 )
dependencies: Autobump spinnakerGradleVersion (#989) ( 325886ad )

Front50 2.25.4

Other

dependencies: Autobump fiatVersion ( 47b98338 )
dependencies: Autobump korkVersion ( cdc14e42 )

Gate 6.55.4

Other

dependencies: Autobump fiatVersion ( be97e2ad )
dependencies: Autobump korkVersion ( 338034da )

Igor 4.7.4

Other

dependencies: Autobump fiatVersion ( b65b0d50 )
dependencies: Autobump korkVersion ( 81ca4033 )

Kayenta 2.32.4

Other

dependencies: Autobump orcaVersion ( c99c5f1e )

Orca 8.24.5

Fixes

conflict: Fix merge conflict ( 107ff38d )
timeout: Added feature flag for rollback timeout ui input. (backport #4383) ( 107ff38d )
timeout: Added feature flag for rollback timeout ui input. ( 107ff38d )
timeout: Added feature flag for rollback timeout ui input. ( 107ff38d )
timeout: Added feature flag for rollback timeout ui input. ( 107ff38d )
timeout: Added feature flag for rollback timeout ui input. ( 107ff38d )

Other

dependencies: Autobump fiatVersion ( 66ef088a )
dependencies: Autobump korkVersion ( 09b15367 )

Rosco 1.8.6

Other

dependencies: Autobump korkVersion ( 17d001df )

Spinnaker Release 1.27.4

Wed, 01 Mar 2023 19:07:12 +0000

Clouddriver 5.74.6

Features

gke: Enables gcloud auth plugin for 1.26+ GKE clusters (backport #5847) ( 79ee9e88 )
gke: Enables gcloud auth plugin for 1.26+ GKE clusters ( 79ee9e88 )
gke: Enables gcloud auth plugin for 1.26+ GKE clusters ( 79ee9e88 )
gke: Bump google cloud sdk and add the plugin for GKE 1.26+ ( 79ee9e88 )

Fixes

ecr: Two credentials with same accountId confuses EcrImageProvider with different regions (#5885) ( 4c957848 )
test: Make the regions reasonable here too ( 4c957848 )

Other

dependencies: Autobump fiatVersion ( b6cfc3b3 )
dependencies: Autobump korkVersion ( 2d0d6e01 )
dependencies: pin version of com.github.tomakehurst:wiremock (#5845) ( b6a03baf )
merge: fix merge conflict in backport ( 79ee9e88 )

Deck 3.8.5

Fixes

timeout: Added feature flag for rollback timeout ui input. (backport #9937) ( 91df4ee6 )
timeout: Added feature flag for rollback timeout ui input. ( 91df4ee6 )
timeout: Added feature flag for rollback timeout ui input. ( 91df4ee6 )
timeout: Added feature flag for rollback timeout ui input. ( 91df4ee6 )
timeout: Added feature flag for rollback timeout ui input. ( 91df4ee6 )
timeout: Added feature flag for rollback timeout ui input. ( 91df4ee6 )
timeout: Added feature flag for rollback timeout ui input. ( 91df4ee6 )

Echo 2.32.6

Features

event: Add circuit breaker for events sending. (#1233) ( 5c2e4d7b )
event: Add circuit breaker for events sending. ( 5c2e4d7b )

Fixes

fix: The circuit breaker feature for sending events to telemetry endpoint is hidden under a required feature flag property (#1241) ( 4e1eca56 )

Other

dependencies: Autobump fiatVersion ( 809a1831 )
dependencies: Autobump korkVersion ( eef351c8 )

Fiat 1.28.12

Other

dependencies: Autobump korkVersion ( a52e5a98 )

Front50 2.23.9

Other

dependencies: Autobump fiatVersion ( adfd0b79 )
dependencies: Autobump korkVersion ( 661a4014 )

Gate 6.54.7

Other

dependencies: Autobump fiatVersion ( b8360a01 )
dependencies: Autobump korkVersion ( 4875a920 )

Igor 4.6.7

Other

dependencies: Autobump fiatVersion ( 11b9dcd1 )
dependencies: Autobump korkVersion ( 8ff0efd2 )

Kayenta 2.31.5

Other

dependencies: Autobump orcaVersion ( a67db92f )

Orca 8.18.9

Fixes

timeout: Added feature flag for rollback timeout ui input. (backport #4383) ( 9ea6baaf )
timeout: Added feature flag for rollback timeout ui input. ( 9ea6baaf )
timeout: Added feature flag for rollback timeout ui input. ( 9ea6baaf )
timeout: Added feature flag for rollback timeout ui input. ( 9ea6baaf )
timeout: Added feature flag for rollback timeout ui input. ( 9ea6baaf )
timeout: Added feature flag for rollback timeout ui input. ( 9ea6baaf )

Other

dependencies: Autobump fiatVersion ( c990e356 )
dependencies: Autobump korkVersion ( 2c26b657 )

Rosco 1.7.8

Other

dependencies: Autobump korkVersion ( 7310481c )

Spinnaker Release 1.29.2

Fri, 09 Dec 2022 00:03:29 +0000

Rosco 1.12.2

Features

core: add aws.bakery-defaults.maskedPackerParameters configuration parameter ( defc9510 )

Other

core: verify that JobRequest.maskedTokenizedCommand really masks ( defc9510 )

Spinnaker Release 1.28.4

Thu, 08 Dec 2022 23:54:08 +0000

Rosco 1.8.5

Features

core: add aws.bakery-defaults.maskedPackerParameters configuration parameter ( 577d19c6 )

Other

core: verify that JobRequest.maskedTokenizedCommand really masks ( 577d19c6 )

Spinnaker Release 1.27.3

Thu, 08 Dec 2022 23:44:11 +0000

Rosco 1.7.7

Features

core: add aws.bakery-defaults.maskedPackerParameters configuration parameter ( 713d1944 )

Other

core: verify that JobRequest.maskedTokenizedCommand really masks ( 713d1944 )

Spinnaker Release 1.29.1

Tue, 06 Dec 2022 23:12:02 +0000

Clouddriver 5.78.3

Fixes

appengine: Fixes app engine credentials repo (#5807) ( 7363ab07 )
artifacts/bitbuket: added ACCEPT Header when using token auth (#5813) ( c3b4ef22 )
artifacts/bitbuket: added ACCEPT Header when using token auth ( c3b4ef22 )
artifacts/bitbuket: changed for constant MediaType.APPLICATION_JSON_VALUE ( c3b4ef22 )
artifacts/bitbuket: added ‘Accept: application/json’ header on unit tests ( c3b4ef22 )
core: Remove payload data from logs (#5784) ( e799bab3 )
google: Fix for the missing CredentialsRepository issue (#5793) ( 67ce8c8d )
google: Fix for the missing CredentialsRepository issue ( 67ce8c8d )
google: Fix for the missing CredentialsRepository issue. Added test. ( 67ce8c8d )
kubernetes: teach KubernetesManifest to support kubernetes resources where the spec is not a map (#5814) ( 60152a57 )
kubernetes: teach KubernetesManifest to support kubernetes resources where the spec is not a map ( 60152a57 )

Other

configserver: use version 0.14.2 of com.github.wnameless.json:json-flattener (#5804) ( 760c996e )
dependencies: Autobump fiatVersion ( dc7b626b )
dependencies: Autobump korkVersion ( e8a776db )
dependencies: Autobump spinnakerGradleVersion (#5819) ( 65741f98 )
dependencies: don’t create an autobump PR for halyard on a clouddriver release branch (#5677) ( 002e9e37 )
kubernetes: verify that KubernetesDeployManifestOperation can deploy a custom resource whose spec is a list ( 60152a57 )

Deck 3.12.1

Features

pipeline: added feature flag for pipeline when mj stage child (#9914) ( 30cb2e22 )
pipeline: added feature flag for pipeline when mj stage child ( 30cb2e22 )

Fixes

aws: Fixing bugs related to clone CX when instance types are incompatible with image/region (#9901) ( f2c0467e )
aws: Fixing bugs related to clone UX when instance types are incompatible with image/region ( f2c0467e )
aws: PR feedback ( f2c0467e )
aws: fix instance type selector by allowing instance types that can’t be validated. (#9893) ( eeed4998 )
aws: fix instance type selector by allowing instance types that can’t be validated. ( eeed4998 )
aws: adding test for instance type selector fix ( eeed4998 )
core: Do not set static document base URL (#9890) ( a078cc1c )
links: update link to spinnaker release changelog (#9897) ( c3ea5bce )
links: update link to spinnaker release changelog ( c3ea5bce )
pipeline: added verification for sub pipe data ( 30cb2e22 )

Other

dependencies: Autobump spinnakerGradleVersion (#9916) ( ab3cb6e0 )

Echo 2.36.1

Features

webhooks: Handle Bitbucket Server PR events ( 8ddbbfb5 )

Other

dependencies: Autobump fiatVersion ( 8dcc9578 )
dependencies: Autobump korkVersion ( 7ef48ce9 )
dependencies: Autobump spinnakerGradleVersion (#1215) ( 055ba9fe )

Fiat 1.36.1

Other

dependencies: Autobump korkVersion ( 0282fe2b )
dependencies: Autobump spinnakerGradleVersion (#989) ( 889372b3 )

Front50 2.27.1

Fixes

pipelines: prevent from creating duplicated pipelines (#1172) ( 7ff4ef9b )
pipelines: prevent from duplicated pipelines ( 7ff4ef9b )

Other

dependencies: Autobump fiatVersion ( ad068354 )
dependencies: Autobump korkVersion ( 691cb0a0 )
dependencies: Autobump spinnakerGradleVersion (#1177) ( 01e19847 )
dependencies: don’t create an autobump PR for halyard on a front50 release branch (#1115) ( 0819232e )

Gate 6.57.1

Other

dependencies: Autobump fiatVersion ( abba1506 )
dependencies: Autobump korkVersion ( 052af099 )
dependencies: Autobump spinnakerGradleVersion (#1585) ( e63560ae )

Igor 4.10.1

Other

dependencies: Autobump fiatVersion ( 23b17027 )
dependencies: Autobump korkVersion ( 7ae82777 )
dependencies: Autobump spinnakerGradleVersion (#1055) ( 31c92aa8 )

Kayenta 2.35.1

Fixes

security: Bump commons-text for CVE-2022-42889 (#911) ( 2a8436fa )
security: Bump commons-text for CVE-2022-42889 ( 2a8436fa )
version: Add patch version not just minor version ( 2a8436fa )

Other

dependencies: Autobump orcaVersion ( 8317e470 )
dependencies: Autobump spinnakerGradleVersion (#917) ( 40701adb )

Orca 8.27.1

Features

bakery: Clean up cached data created by Rosco. (#4323) ( a5135542 )
featureFlags: pass ExpressionProperties to ExpressionsSupport ( ee451cff )

Fixes

config: add back public visibility for ClouddriverRetrofitBuilder class (#4331) ( 5570885c )
config: restore prior visibility of methods on CloudDriverConfigurationProperties class (#4317) ( 3ac8a175 )
stageExecution: In evaluable variable stage restart scenario variables are not cleaned properly (#16) (backport #4307) ( 5dc39202 )
tasks: Fix MonitorKayentaCanaryTask on results data map (#4312) ( 04885fd8 )

Other

dependencies: Autobump fiatVersion ( e534be63 )
dependencies: Autobump korkVersion ( ee451cff )
dependencies: Autobump korkVersion ( ee451cff )
dependencies: Autobump spinnakerGradleVersion (#4337) ( b4c8041b )

Rosco 1.12.1

Features

bakery: Clean up cached data created by Rosco. (#912) ( 4513c617 )
bakery: Clean up cached data created by Rosco. ( 4513c617 )

Other

dependencies: Autobump korkVersion ( 5dafb668 )
dependencies: Autobump spinnakerGradleVersion (#917) ( 79471720 )

Spinnaker Release 1.28.3

Tue, 06 Dec 2022 22:53:29 +0000

Echo 2.34.4

Features

webhooks: Handle Bitbucket Server PR events ( 6d1e3f97 )

Spinnaker Release 1.28.2

Tue, 06 Dec 2022 17:18:49 +0000

Clouddriver 5.76.3

Fixes

appengine: Fixes app engine credentials repo (#5807) ( 68cfc352 )
artifacts/bitbuket: added ACCEPT Header when using token auth (#5813) ( cbe7bca5 )
artifacts/bitbuket: added ACCEPT Header when using token auth ( cbe7bca5 )
artifacts/bitbuket: changed for constant MediaType.APPLICATION_JSON_VALUE ( cbe7bca5 )
artifacts/bitbuket: added ‘Accept: application/json’ header on unit tests ( cbe7bca5 )
core: Remove payload data from logs (#5784) ( 1a5d4861 )
kubernetes: teach KubernetesManifest to support kubernetes resources where the spec is not a map (#5814) ( 61858506 )
kubernetes: teach KubernetesManifest to support kubernetes resources where the spec is not a map ( 61858506 )

Other

configserver: use version 0.14.2 of com.github.wnameless.json:json-flattener (#5804) ( d7d0c5ab )
dependencies: Autobump spinnakerGradleVersion (#5819) ( b12e1dec )
dependencies: Autobump fiatVersion ( 0f5a2756 )
dependencies: Autobump korkVersion ( f4cb5712 )
kubernetes: verify that KubernetesDeployManifestOperation can deploy a custom resource whose spec is a list ( 61858506 )

Deck 3.9.2

Features

pipeline: added feature flag for pipeline when mj stage child (backport #9914) ( f889c718 )
pipeline: added feature flag for pipeline when mj stage child ( f889c718 )
pipeline: added feature flag for pipeline when mj stage child ( f889c718 )

Fixes

backport/changes: resolved merge conflicts ( f889c718 )
core: Do not set static document base URL (#9890) ( 817299b2 )
links: update link to spinnaker release changelog (#9897) ( 069dca2e )
links: update link to spinnaker release changelog ( 069dca2e )
pipeline: added verification for sub pipe data ( f889c718 )
search: Error thrown when search version 2 is enabled (#9888) ( 102be816 )

Other

core/pipelines: Fix syntax error on ui-select causing stage configuration to not load (backport #9886) ( 4debc5fc )
dependencies: Autobump spinnakerGradleVersion (#9916) ( 4c52558c )
pipelinegraph: Improve the performance of the pipeline graph rendering (backport #9871) ( 286a9b5a )

Echo 2.34.3

Other

dependencies: Autobump spinnakerGradleVersion (#1215) ( fec59165 )
dependencies: Autobump fiatVersion ( a335ed4a )
dependencies: Autobump korkVersion ( 7e9bb103 )

Fiat 1.31.3

Fixes

fix: add migration to ensure consistency between resource_name in fiat_resource and fiat_permission tables (backport #964) ( 907d0d78 )
permissions: ensure lower case for resource name in fiat_permission and fiat_resource tables (backport #963) ( f1a6a114 )
roles: Ensure account manager role is cached (backport #960) ( 67a30525 )

Other

dependencies: Autobump korkVersion ( 7a5d6445 )

Front50 2.25.3

Fixes

pipelines: prevent from creating duplicated pipelines (#1172) ( 92566bad )
pipelines: prevent from duplicated pipelines ( 92566bad )
updateTs: missing updateTs field in the get pipeline history’s response. (backport #1159) ( e4698fb8 )

Other

dependencies: Autobump spinnakerGradleVersion (#1177) ( c50094ed )
dependencies: Autobump fiatVersion ( dc963530 )
dependencies: Autobump korkVersion ( 5755fb2d )

Gate 6.55.3

Other

dependencies: Autobump spinnakerGradleVersion (#1585) ( 12965f21 )
dependencies: Autobump fiatVersion ( 64f64567 )
dependencies: Autobump korkVersion ( c7207a1a )

Igor 4.7.3

Features

jenkins: Stop Jenkins job when job name has slashes in the job name (backport #1038) ( c6801bed )

Other

dependencies: Autobump spinnakerGradleVersion (#1055) ( 90f72f8e )
dependencies: Autobump fiatVersion ( 010288b7 )
dependencies: Autobump korkVersion ( c9b6c86d )

Kayenta 2.32.3

Fixes

security: Bump commons-text for CVE-2022-42889 (#911) ( 53792f14 )
security: Bump commons-text for CVE-2022-42889 ( 53792f14 )
version: Add patch version not just minor version ( 53792f14 )

Other

dependencies: Autobump orcaVersion ( b90c7034 )
dependencies: Autobump spinnakerGradleVersion (#917) ( 05f1f767 )

Orca 8.24.4

Features

bakery: Clean up cached data created by Rosco. (#4323) ( 8a8d2712 )
featureFlags: pass ExpressionProperties to ExpressionsSupport ( c69ccc78 )
igor: Stop Jenkins job when job name has slashes in the job name (backport #4294) ( b2fa8161 )

Fixes

stage: Resource requests on custom stage | Error: got “map”, expected “string…” (backport #4295) ( 6405f430 )
stageExecution: In evaluable variable stage restart scenario variables are not cleaned properly (#16) (backport #4307) ( 3cb7128b )
tasks: Fix MonitorKayentaCanaryTask on results data map (#4312) ( 447ffbb1 )

Other

dependencies: Autobump spinnakerGradleVersion (#4337) ( 89fdccc7 )
dependencies: Autobump korkVersion ( c69ccc78 )
dependencies: Autobump korkVersion ( c69ccc78 )
dependencies: Autobump fiatVersion ( 2c561762 )

Rosco 1.8.4

Features

bakery: Clean up cached data created by Rosco. (#912) ( 10dd75a3 )
bakery: Clean up cached data created by Rosco. ( 10dd75a3 )

Other

dependencies: Autobump spinnakerGradleVersion (#917) ( f1e67bed )
dependencies: Autobump korkVersion ( e96cae46 )

Spinnaker Release 1.27.2

Fri, 02 Dec 2022 06:26:36 +0000

Clouddriver 5.74.5

Fixes

core: Remove payload data from logs (#5784) ( 72204fd2 )
kubernetes: teach KubernetesManifest to support kubernetes resources where the spec is not a map (#5814) ( 75469726 )
kubernetes: teach KubernetesManifest to support kubernetes resources where the spec is not a map ( 75469726 )

Other

dependencies: Autobump spinnakerGradleVersion (#5819) ( b1cd0554 )
dependencies: Autobump fiatVersion ( b15ef986 )
kubernetes: verify that KubernetesDeployManifestOperation can deploy a custom resource whose spec is a list ( 75469726 )

Deck 3.8.4

Fixes

links: update link to spinnaker release changelog (#9897) ( c49b64e0 )
links: update link to spinnaker release changelog ( c49b64e0 )

Other

dependencies: Autobump spinnakerGradleVersion (#9916) ( c7ac4908 )

Echo 2.32.5

Other

dependencies: Autobump spinnakerGradleVersion (#1215) ( 303a55fb )
dependencies: Autobump fiatVersion ( b1bf2fcb )

Fiat 1.28.11

Fixes

permissions: ensure lower case for resource name in fiat_permission and fiat_resource tables (backport #963) ( 523c5fc7 )

Other

Cleanup publish debugging ( 52351b04 )
build: set timeout for apt publishing to 10 minutes and add –stacktrace ( 78857646 )
build: set timeout for apt publishing to 5 minutes ( 9ad1d221 )
dependencies: Autobump spinnakerGradleVersion (#989) ( 3d0a6096 )

Front50 2.23.8

Fixes

pipelines: prevent from creating duplicated pipelines (#1172) ( 296df6d2 )
pipelines: prevent from duplicated pipelines ( 296df6d2 )
updateTs: missing updateTs field in the get pipeline history’s response. (backport #1159) ( 67c64e8a )

Other

dependencies: Autobump spinnakerGradleVersion (#1177) ( 6f8c4c3f )
dependencies: Autobump fiatVersion ( 5ed74997 )
gha: bump versions of github actions ( 462b6807 )

Gate 6.54.6

Other

dependencies: Autobump spinnakerGradleVersion (#1585) ( 39f63f56 )
dependencies: Autobump fiatVersion ( 84dac9de )
gha: bump versions of github actions ( 4d90c871 )

Igor 4.6.6

Features

jenkins: Stop Jenkins job when job name has slashes in the job name (backport #1038) ( dd51bfcd )

Other

dependencies: Autobump spinnakerGradleVersion (#1055) ( 6fa3a871 )
dependencies: Autobump fiatVersion ( 35c25f7f )

Kayenta 2.31.4

Fixes

security: Bump commons-text for CVE-2022-42889 (#911) ( f440527e )
security: Bump commons-text for CVE-2022-42889 ( f440527e )
version: Add patch version not just minor version ( f440527e )

Other

dependencies: Autobump spinnakerGradleVersion (#917) ( fa061cad )
dependencies: Autobump orcaVersion ( e755ba49 )
dependencies: Autobump orcaVersion ( 6c622b5c )

Orca 8.18.8

Features

bakery: Clean up cached data created by Rosco. (#4323) ( 91f6247b )
igor: Stop Jenkins job when job name has slashes in the job name (backport #4294) ( be402b35 )

Fixes

stage: Resource requests on custom stage | Error: got “map”, expected “string…” (backport #4295) ( c055dd00 )
stageExecution: In evaluable variable stage restart scenario variables are not cleaned properly (#16) (backport #4307) ( 1a601449 )
tasks: Fix MonitorKayentaCanaryTask on results data map (#4312) ( a0d83ffe )

Other

dependencies: Autobump spinnakerGradleVersion (#4337) ( 9709ee0c )
dependencies: Autobump fiatVersion ( e9da9f6e )

Rosco 1.7.6

Features

bakery: Clean up cached data created by Rosco. (#912) ( 5cb10c89 )
bakery: Clean up cached data created by Rosco. ( 5cb10c89 )

Fixes

install: Fixed bugs in postInstall script that causes installation to fail on Ubuntu 20.04 and 22.04 LTS (#899) ( 92174813 )

Other

dependencies: Autobump spinnakerGradleVersion (#917) ( 1becf314 )

Spinnaker Release 1.29.0

Tue, 04 Oct 2022 21:03:53 +0000

Changelog

Note: This release requires Halyard version 1.45.0 or later.

Spring Boot 2.3

Spinnaker 1.29 uses Spring Boot 2.3, where 1.28 uses Spring Boot 2.2. Spring Boot 2.3 considers session data cached by Spring Boot 2.2 invalid. Therefore, users with cached sessions will be unable to log in until the invalid information is removed from the cache. Open browser windows to Spinnaker are unresponsive after the deployment until they’re reloaded. Executing:

Spinnaker Release 1.28.1

Tue, 23 Aug 2022 18:49:38 +0000

Rosco 1.8.3

Other

ci: Upload halconfigs to GCS on Tag push (#873) ( a22e118a )

Spinnaker Release 1.28.0

Sun, 21 Aug 2022 23:26:44 +0000

Note: This release requires Halyard version 1.45.0 or later.

Clouddriver

There are a number of changes to reduce clouddriver’s startup time:
- don't load namespaces in k8s accounts (with kubernetes.loadNamespacesInAccount: false)
- parse aws accounts in multiple threads (with aws.loadAccounts.multiThreadingEnabled: true)
- cache regions when parsing aws accounts
The sharding configuration properties used for sql based implementation are updated to make it consistent with redis based implementation. Now, the following configuration applies to both the implementations.

Spinnaker Release 1.27.1

Thu, 18 Aug 2022 21:14:56 +0000

Clouddriver 5.74.4

Fixes

caching: K8s cache affected when not enough permissions in service account (backport #5742) ( 6416718b )
ci: fetch previous tag from git instead of API (#5696) ( 2445666c )

Other

ci: Mergify - merge Autobumps on release-* (#5697) ( 17fec14f )
dependencies: Autobump fiatVersion ( 99cb178a )
dockerfile: upgrade to latest alpine image (#5758) ( aabbda05 )
titus: limit protobuf to 3.17.3 (#5706) ( e25048ca )

Deck 3.8.3

Features

core: Synchronize the verticalNavExpandedAtom using an atom effect (backport #9859) ( 0417e97f )

Echo 2.32.4

Fixes

ci: fetch previous tag from git instead of API (#1181) ( 77fa4204 )

Other

ci: Mergify - merge Autobumps on release-* (#1182) ( 6a42b629 )
dependencies: Autobump fiatVersion ( 2fa1bccf )
dockerfile: upgrade to latest alpine image (#1193) ( 5a171294 )

Fiat 1.28.5

Fixes

ci: fetch previous tag from git instead of API (#948) ( 52a8f520 )

Other

build: specify an artifact for bumpdeps to look for (backport #916) ( 0f949339 )
build: specify an artifact for bumpdeps to look for ( 0f949339 )
dockerfile: upgrade to latest alpine image (#967) ( d27a99e4 )

Front50 2.23.4

Fixes

fix: Revision history is not showing the timestamp of the revision (backport #1142) ( 19566df7 )
ci: fetch previous tag from git instead of API (#1127) ( 59b8723d )

Other

ci: Mergify - merge Autobumps on release-* (#1128) ( c36b9051 )
dependencies: Autobump fiatVersion ( 1fc1c667 )
dockerfile: upgrade to latest alpine image (backport #1151) ( abeb6718 )

Gate 6.54.3

Fixes

ci: fetch previous tag from git instead of API (#1551) ( ef6eadeb )

Other

ci: Mergify - merge Autobumps on release-* (#1552) ( c2972d12 )
dependencies: Autobump fiatVersion ( c8bcc768 )
dockerfile: upgrade to latest alpine image (#1564) ( 7ce04bcb )

Igor 4.6.5

Fixes

ci: fetch previous tag from git instead of API (#1017) ( e82d299e )

Other

ci: Mergify - merge Autobumps on release-* (#1018) ( d695313e )
dependencies: Autobump fiatVersion ( 3c606de4 )
dockerfile: upgrade to latest alpine image (#1030) ( bbb6861e )

Kayenta 2.31.3

Fixes

ci: fetch previous tag from git instead of API (#888) ( 994d0a50 )

Other

ci: Mergify - merge Autobumps on release-* (#889) ( 85a1eb39 )
dependencies: Autobump orcaVersion ( 4ed88356 )
dockerfile: upgrade to latest alpine image (#900) ( 558550a0 )

Orca 8.18.5

Fixes

ci: fetch previous tag from git instead of API (#4263) ( ac31f337 )

Other

ci: Mergify - merge Autobumps on release-* (#4264) ( 7145e8a3 )
dependencies: Autobump fiatVersion ( 0c195d77 )
dockerfile: upgrade to latest alpine image (#4284) ( 728f29cb )

Rosco 1.7.5

Fixes

ci: fetch previous tag from git instead of API (#877) ( 1256d50d )

Other

ci: Mergify - merge Autobumps on release-* (#878) ( 866e9c69 )
ci: Mergify - merge Autobumps on release-* ( 866e9c69 )
ci: Merge Autobumps simpler regex ( 866e9c69 )
dockerfile: upgrade to latest alpine image (backport #894) ( c12dfb8f )

Spinnaker Release 1.27.0

Mon, 02 May 2022 23:37:12 +0000

Spinnaker Release 1.26.7

Wed, 15 Dec 2021 01:05:17 +0000

Spinnaker Release 1.25.8

Wed, 15 Dec 2021 00:50:12 +0000

Spinnaker Release 1.24.6

Thu, 01 Jul 2021 20:40:34 +0000

Spinnaker Release 1.26.5

Thu, 01 Jul 2021 00:49:04 +0000

Spinnaker Release 1.26.6

Thu, 01 Jul 2021 00:49:04 +0000

Spinnaker Release 1.25.7

Sat, 26 Jun 2021 08:01:26 +0000

Spinnaker Release 1.26.4

Fri, 18 Jun 2021 20:39:56 +0000

Spinnaker Release 1.25.6

Fri, 18 Jun 2021 20:22:00 +0000

Spinnaker Release 1.25.5

Thu, 27 May 2021 09:04:10 +0000

Spinnaker Release 1.24.5

Thu, 27 May 2021 08:56:51 +0000

Spinnaker Release 1.26.3

Thu, 13 May 2021 19:16:04 +0000

Spinnaker Release 1.26.2

Mon, 03 May 2021 23:49:27 +0000

Spinnaker Release 1.26.1

Thu, 29 Apr 2021 18:34:42 +0000

Spinnaker Release 1.26.0

Fri, 23 Apr 2021 22:04:51 +0000

Spinnaker Release 1.25.4

Thu, 01 Apr 2021 02:38:40 +0000

Spinnaker Release 1.25.3

Mon, 22 Mar 2021 20:40:39 +0000

Spinnaker Release 1.25.2

Tue, 09 Mar 2021 07:57:50 +0000

Spinnaker Release 1.25.1

Wed, 03 Mar 2021 08:29:00 +0000

Spinnaker Release 1.25.0

Tue, 23 Feb 2021 22:05:06 +0000

Spinnaker Release 1.23.7

Fri, 19 Feb 2021 01:25:30 +0000

Spinnaker Release 1.24.4

Wed, 03 Feb 2021 23:13:08 +0000

Spinnaker Release 1.23.6

Thu, 28 Jan 2021 14:39:41 +0000

Spinnaker Release 1.22.6

Thu, 28 Jan 2021 02:11:57 +0000

Spinnaker Release 1.24.3

Wed, 27 Jan 2021 15:40:26 +0000

Spinnaker Release 1.22.5

Tue, 26 Jan 2021 23:06:26 +0000

Spinnaker Release 1.24.2

Wed, 06 Jan 2021 18:32:52 +0000

Spinnaker Release 1.24.1

Mon, 21 Dec 2020 23:36:25 +0000

Spinnaker Release 1.24.0

Mon, 14 Dec 2020 20:34:17 +0000

Spinnaker Release 1.23.5

Mon, 14 Dec 2020 19:08:41 +0000

Spinnaker Release 1.23.4

Tue, 08 Dec 2020 16:31:32 +0000

Spinnaker Release 1.22.4

Tue, 08 Dec 2020 14:56:16 +0000

Spinnaker Release 1.21.5

Mon, 07 Dec 2020 23:09:05 +0000

Spinnaker Release 1.23.3

Tue, 01 Dec 2020 18:37:53 +0000

Spinnaker Release 1.22.3

Tue, 01 Dec 2020 17:26:40 +0000

Spinnaker Release 1.23.2

Mon, 16 Nov 2020 17:26:41 +0000

Spinnaker Release 1.23.1

Tue, 03 Nov 2020 14:34:07 +0000

Spinnaker Release 1.23.0

Tue, 20 Oct 2020 16:38:34 +0000

Spinnaker Release 1.22.2

Tue, 13 Oct 2020 15:18:00 +0000

Spinnaker Release 1.22.1

Mon, 31 Aug 2020 14:48:37 +0000

Spinnaker Release 1.22.0

Mon, 24 Aug 2020 16:10:02 +0000

Spinnaker Release 1.19.14

Thu, 13 Aug 2020 23:44:46 +0000

Spinnaker Release 1.21.4

Thu, 13 Aug 2020 00:23:38 +0000

Spinnaker Release 1.20.8

Thu, 13 Aug 2020 00:20:30 +0000

Spinnaker Release 1.21.3

Sat, 08 Aug 2020 00:08:18 +0000

Spinnaker Release 1.19.13

Tue, 28 Jul 2020 01:22:03 +0000

Spinnaker Release 1.21.2

Fri, 24 Jul 2020 02:06:47 +0000

Spinnaker Release 1.20.7

Wed, 22 Jul 2020 22:22:44 +0000

Spinnaker Release 1.21.1

Wed, 22 Jul 2020 17:46:16 +0000

Spinnaker Release 1.19.12

Tue, 30 Jun 2020 20:38:40 +0000

Spinnaker Release 1.21.0

Mon, 29 Jun 2020 18:46:10 +0000

Spinnaker Release 1.20.6

Thu, 25 Jun 2020 17:12:29 +0000

Spinnaker Release 1.20.5

Mon, 08 Jun 2020 15:10:44 +0000

Spinnaker Release 1.20.4

Mon, 01 Jun 2020 16:56:02 +0000

Spinnaker Release 1.19.11

Mon, 01 Jun 2020 14:38:23 +0000

Spinnaker Release 1.20.3

Tue, 26 May 2020 15:33:27 +0000

Spinnaker Release 1.19.10

Tue, 26 May 2020 13:04:08 +0000

Spinnaker Release 1.18.12

Tue, 26 May 2020 13:00:37 +0000

Spinnaker Release 1.19.9

Tue, 19 May 2020 13:43:05 +0000

Spinnaker Release 1.20.2

Mon, 18 May 2020 14:29:08 +0000

Spinnaker Release 1.20.1

Mon, 11 May 2020 13:19:23 +0000

Spinnaker Release 1.19.8

Mon, 11 May 2020 13:15:12 +0000

Spinnaker Release 1.18.11

Mon, 11 May 2020 13:10:33 +0000

Spinnaker Release 1.18.10

Tue, 05 May 2020 13:46:33 +0000

Spinnaker Release 1.19.7

Tue, 05 May 2020 11:53:08 +0000

Spinnaker Release 1.20.0

Mon, 04 May 2020 17:59:33 +0000

Spinnaker Release 1.19.6

Thu, 23 Apr 2020 15:53:53 +0000

Spinnaker Release 1.19.5

Wed, 15 Apr 2020 18:04:36 +0000

Spinnaker Release 1.18.9

Wed, 15 Apr 2020 18:01:42 +0000

Spinnaker Release 1.19.4

Fri, 03 Apr 2020 18:58:22 +0000

Spinnaker Release 1.18.8

Fri, 03 Apr 2020 18:55:22 +0000

Spinnaker Release 1.17.10

Fri, 03 Apr 2020 18:52:34 +0000

Spinnaker Release 1.19.3

Mon, 30 Mar 2020 23:00:57 +0000

Spinnaker Release 1.18.7

Mon, 30 Mar 2020 22:44:12 +0000

Spinnaker Release 1.17.9

Mon, 30 Mar 2020 20:54:12 +0000

Spinnaker Release 1.19.2

Fri, 20 Mar 2020 21:17:01 +0000

Spinnaker Release 1.17.8

Fri, 20 Mar 2020 20:17:31 +0000

Spinnaker Release 1.18.6

Mon, 16 Mar 2020 21:58:05 +0000

Spinnaker Release 1.19.1

Mon, 16 Mar 2020 21:54:51 +0000

Spinnaker Release 1.19.0

Wed, 11 Mar 2020 20:23:08 +0000

Spinnaker Release 1.18.5

Mon, 09 Mar 2020 19:44:10 +0000

Spinnaker Release 1.17.7

Mon, 09 Mar 2020 19:37:53 +0000

Spinnaker Release 1.16.7

Mon, 09 Mar 2020 19:34:42 +0000

Spinnaker Release 1.18.4

Thu, 27 Feb 2020 21:59:13 +0000

Spinnaker Release 1.18.3

Thu, 20 Feb 2020 18:36:42 +0000

Spinnaker Release 1.18.2

Mon, 10 Feb 2020 14:31:18 +0000

Spinnaker Release 1.18.1

Fri, 31 Jan 2020 19:10:30 +0000

Spinnaker Release 1.18.0

Wed, 22 Jan 2020 13:18:57 +0000

Spinnaker Release 1.17.6

Tue, 14 Jan 2020 14:19:54 +0000

Spinnaker Release 1.17.5

Mon, 16 Dec 2019 21:21:31 +0000

Spinnaker Release 1.17.4

Thu, 12 Dec 2019 15:31:46 +0000

Spinnaker Release 1.15.7

Tue, 03 Dec 2019 11:41:43 +0000

Spinnaker Release 1.16.6

Tue, 03 Dec 2019 10:37:55 +0000

Spinnaker Release 1.17.3

Tue, 03 Dec 2019 08:51:01 +0000

Spinnaker Release 1.17.2

Wed, 20 Nov 2019 11:15:31 +0000

Spinnaker Release 1.16.5

Mon, 11 Nov 2019 13:59:16 +0000

Spinnaker Release 1.17.1

Mon, 11 Nov 2019 12:45:00 +0000

Spinnaker Release 1.17.0

Mon, 04 Nov 2019 14:07:43 +0000

Spinnaker Release 1.15.6

Wed, 23 Oct 2019 16:58:57 +0000

Spinnaker Release 1.16.4

Wed, 23 Oct 2019 16:53:30 +0000

Spinnaker Release 1.16.3

Mon, 14 Oct 2019 15:07:32 +0000

Spinnaker Release 1.15.5

Tue, 01 Oct 2019 17:12:01 +0000

Spinnaker Release 1.16.2

Tue, 01 Oct 2019 17:08:45 +0000

Spinnaker Release 1.16.1

Tue, 17 Sep 2019 13:48:16 +0000

Spinnaker Release 1.15.4

Tue, 17 Sep 2019 13:36:04 +0000

Spinnaker Release 1.14.15

Mon, 16 Sep 2019 14:09:59 +0000

Spinnaker Release 1.16.0

Mon, 09 Sep 2019 10:52:30 +0000

Spinnaker Release 1.15.3

Mon, 26 Aug 2019 17:09:31 +0000

Spinnaker Release 1.14.14

Wed, 14 Aug 2019 09:38:01 +0000

Spinnaker Release 1.15.2

Mon, 12 Aug 2019 16:49:02 +0000

Spinnaker Release 1.14.13

Mon, 05 Aug 2019 10:39:41 +0000

Spinnaker Release 1.13.12

Mon, 29 Jul 2019 14:19:09 +0000

Spinnaker Release 1.14.12

Mon, 29 Jul 2019 13:41:43 +0000

Spinnaker Release 1.15.1

Mon, 29 Jul 2019 13:04:12 +0000

Spinnaker Release 1.14.11

Tue, 23 Jul 2019 17:50:37 +0000

Spinnaker Release 1.15.0

Fri, 19 Jul 2019 13:28:47 +0000

Spinnaker Release 1.14.10

Thu, 18 Jul 2019 12:07:45 +0000

Spinnaker Release 1.14.9

Mon, 08 Jul 2019 17:11:13 +0000

Spinnaker Release 1.12.14

Mon, 08 Jul 2019 10:47:01 +0000

Spinnaker Release 1.13.11

Mon, 08 Jul 2019 09:56:56 +0000

Spinnaker Release 1.14.8

Mon, 01 Jul 2019 10:14:34 +0000

Spinnaker Release 1.14.7

Mon, 24 Jun 2019 10:03:33 +0000

Spinnaker Release 1.13.10

Thu, 20 Jun 2019 11:31:40 +0000

Spinnaker Release 1.12.13

Thu, 20 Jun 2019 11:12:30 +0000

Spinnaker Release 1.14.6

Mon, 17 Jun 2019 12:46:02 +0000

Spinnaker Release 1.14.5

Wed, 12 Jun 2019 10:23:28 +0000

Spinnaker Release 1.13.9

Mon, 10 Jun 2019 14:50:42 +0000

Spinnaker Release 1.14.4

Mon, 10 Jun 2019 12:35:56 +0000

Spinnaker Release 1.12.12

Wed, 05 Jun 2019 14:46:51 +0000

Spinnaker Release 1.14.3

Tue, 04 Jun 2019 11:15:15 +0000

Spinnaker Release 1.14.2

Tue, 28 May 2019 14:57:44 +0000

Spinnaker Release 1.14.1

Fri, 24 May 2019 11:17:23 +0000

Spinnaker Release 1.13.8

Thu, 23 May 2019 15:27:05 +0000

Spinnaker Release 1.12.11

Thu, 23 May 2019 15:17:25 +0000

Spinnaker Release 1.14.0

Mon, 20 May 2019 15:28:53 +0000

Spinnaker Release 1.13.7

Thu, 16 May 2019 13:49:24 +0000

Spinnaker Release 1.11.13

Wed, 01 May 2019 10:38:14 +0000

Spinnaker Release 1.12.10

Mon, 29 Apr 2019 11:39:22 +0000

Spinnaker Release 1.13.6

Mon, 29 Apr 2019 11:35:20 +0000

Spinnaker Release 1.13.5

Mon, 22 Apr 2019 10:32:39 +0000

Spinnaker Release 1.13.4

Mon, 15 Apr 2019 13:22:53 +0000

Spinnaker Release 1.13.1

Tue, 09 Apr 2019 10:31:22 +0000

Spinnaker Release 1.13.3

Tue, 09 Apr 2019 10:11:54 +0000

Spinnaker Release 1.13.2

Fri, 05 Apr 2019 11:46:16 +0000

Spinnaker Release 1.11.12

Fri, 05 Apr 2019 10:55:49 +0000

Spinnaker Release 1.12.9

Fri, 05 Apr 2019 10:11:53 +0000

Spinnaker Release 1.12.8

Mon, 01 Apr 2019 09:48:34 +0000

Spinnaker Release 1.13.0

Mon, 25 Mar 2019 15:38:07 +0000

Spinnaker Release 1.12.7

Fri, 22 Mar 2019 10:16:58 +0000

Spinnaker Release 1.12.6

Wed, 13 Mar 2019 22:37:28 +0000

Spinnaker Release 1.12.5

Fri, 08 Mar 2019 19:43:23 +0000

Spinnaker Release 1.12.4

Fri, 01 Mar 2019 12:55:24 +0000

Spinnaker Release 1.11.11

Fri, 01 Mar 2019 12:46:48 +0000

Spinnaker Release 1.10.14

Fri, 01 Mar 2019 12:43:49 +0000

Spinnaker Release 1.12.3

Mon, 25 Feb 2019 15:41:45 +0000

Spinnaker Release 1.11.10

Mon, 25 Feb 2019 15:39:58 +0000

Spinnaker Release 1.12.2

Thu, 14 Feb 2019 16:17:05 +0000

Spinnaker Release 1.12.1

Thu, 31 Jan 2019 17:01:57 +0000

Spinnaker Release 1.11.9

Wed, 30 Jan 2019 18:27:42 +0000

Spinnaker Release 1.10.13

Wed, 30 Jan 2019 18:25:40 +0000

Spinnaker Release 1.12.0

Mon, 28 Jan 2019 17:13:47 +0000

Spinnaker Release 1.11.8

Mon, 28 Jan 2019 15:33:55 +0000

Spinnaker Release 1.11.7

Tue, 22 Jan 2019 18:38:07 +0000

Spinnaker Release 1.10.12

Tue, 22 Jan 2019 17:55:10 +0000

Spinnaker Release 1.10.11

Tue, 15 Jan 2019 08:41:34 +0000

Spinnaker Release 1.11.6

Tue, 15 Jan 2019 07:29:43 +0000

Spinnaker Release 1.10.10

Fri, 11 Jan 2019 21:23:16 +0000

Spinnaker Release 1.11.5

Fri, 11 Jan 2019 17:45:29 +0000

Spinnaker Release 1.10.9

Sat, 05 Jan 2019 12:44:19 +0000

Spinnaker Release 1.11.4

Sat, 05 Jan 2019 09:17:34 +0000

Spinnaker Release 1.10.8

Fri, 04 Jan 2019 09:24:12 +0000

Spinnaker Release 1.10.7

Thu, 03 Jan 2019 09:58:06 +0000

Spinnaker Release 1.11.3

Thu, 03 Jan 2019 09:36:38 +0000

Spinnaker Release 1.11.2

Fri, 21 Dec 2018 10:49:22 +0000

Spinnaker Release 1.11.1

Wed, 19 Dec 2018 11:44:31 +0000

Spinnaker Release 1.10.6

Wed, 19 Dec 2018 08:00:48 +0000

Spinnaker Release 1.11.0

Thu, 13 Dec 2018 14:49:42 +0000

Spinnaker Release 1.10.5

Thu, 15 Nov 2018 16:46:26 +0000

Spinnaker Release 1.10.4

Mon, 12 Nov 2018 14:27:04 +0000

Spinnaker Release 1.10.3

Fri, 09 Nov 2018 13:55:08 +0000

Spinnaker Release 1.10.2

Mon, 05 Nov 2018 09:38:18 +0000

Spinnaker Release 1.10.1

Wed, 24 Oct 2018 13:04:45 +0000

Spinnaker Release 1.10.0

Tue, 16 Oct 2018 17:31:38 +0000

Spinnaker Release 1.9.5

Mon, 01 Oct 2018 13:15:45 +0000

Spinnaker Release 1.8.7

Fri, 28 Sep 2018 13:58:59 +0000

Spinnaker Release 1.9.4

Wed, 26 Sep 2018 11:33:02 +0000

Spinnaker Release 1.9.3

Mon, 10 Sep 2018 12:14:09 +0000

Spinnaker Release 1.9.2

Wed, 29 Aug 2018 16:08:26 +0000

Spinnaker Release 1.8.6

Wed, 29 Aug 2018 15:11:41 +0000

Spinnaker Release 1.7.8

Wed, 29 Aug 2018 15:10:06 +0000

Spinnaker Release 1.9.1

Tue, 28 Aug 2018 10:13:57 +0000

Spinnaker Release 1.9.0

Wed, 15 Aug 2018 15:49:49 +0000

Spinnaker Release 1.8.5

Thu, 02 Aug 2018 16:40:59 +0000

Spinnaker Release 1.6.2

Thu, 26 Jul 2018 17:55:39 +0000

Spinnaker 1.6.2

Spinnaker Release 1.7.7

Thu, 26 Jul 2018 17:28:13 +0000

Spinnaker 1.7.7

Spinnaker Release 1.8.4

Thu, 26 Jul 2018 16:26:58 +0000

Spinnaker 1.8.4

Spinnaker Release 1.8.3

Tue, 24 Jul 2018 15:36:16 +0000

Spinnaker 1.8.3

Spinnaker Release 1.8.2

Mon, 23 Jul 2018 10:54:30 +0000

Spinnaker 1.8.2

Spinnaker Release 1.8.1

Mon, 09 Jul 2018 16:37:22 +0000

Spinnaker 1.8.1

Spinnaker Release 1.8.0

Fri, 22 Jun 2018 13:48:39 +0000

Spinnaker 1.8.0

Spinnaker Release 1.7.6

Tue, 29 May 2018 12:26:28 +0000

Spinnaker 1.7.6

Spinnaker Release 1.7.5

Mon, 21 May 2018 11:14:10 +0000

Spinnaker 1.7.5

Spinnaker Release 1.7.4

Mon, 14 May 2018 13:03:48 +0000

Spinnaker 1.7.4

Spinnaker Release 1.7.3

Mon, 07 May 2018 13:26:10 +0000

Spinnaker 1.7.3

Spinnaker Release 1.7.2

Tue, 01 May 2018 11:22:26 +0000

Spinnaker 1.7.2

Spinnaker Release 1.7.1

Mon, 30 Apr 2018 13:27:47 +0000

Spinnaker 1.7.1

Spinnaker Release 1.7.0

Wed, 25 Apr 2018 12:06:36 +0000

Spinnaker 1.7.0

Spinnaker Release 1.6.1

Wed, 04 Apr 2018 15:21:03 +0000

Spinnaker 1.6.1

Spinnaker Release 1.6.0

Wed, 21 Feb 2018 22:23:08 +0000

Spinnaker Release 1.5.4

Wed, 10 Jan 2018 18:45:23 +0000

Spinnaker Release 1.5.3

Tue, 09 Jan 2018 20:55:22 +0000

Spinnaker Release 1.5.2

Fri, 22 Dec 2017 17:30:58 +0000

Spinnaker Release 1.5.1

Thu, 30 Nov 2017 21:48:29 +0000

Spinnaker Release 1.5.0

Wed, 08 Nov 2017 18:50:36 +0000

Spinnaker Release 1.4.2

Tue, 03 Oct 2017 17:27:27 +0000

Spinnaker Release 1.4.1

Fri, 22 Sep 2017 18:13:32 +0000

Spinnaker Release 1.4.0

Thu, 21 Sep 2017 20:00:11 +0000

Spinnaker Release 1.3.1

Mon, 18 Sep 2017 16:48:39 +0000

Spinnaker Release 1.3.0

Thu, 07 Sep 2017 21:28:06 +0000

Version 1.3.0 requires Halyard v0.34.0+

Spinnaker Release 1.2.2

Tue, 22 Aug 2017 11:55:01 +0000

Spinnaker Release 1.2.1

Wed, 09 Aug 2017 20:09:52 +0000

Spinnaker Release 1.1.2

Thu, 27 Jul 2017 21:42:06 +0000

Spinnaker Release 1.1.1

Fri, 21 Jul 2017 13:35:55 +0000

Spinnaker Release 1.1.0

Wed, 05 Jul 2017 18:47:56 +0000

Spinnaker Release 1.0.1

Mon, 12 Jun 2017 20:33:32 +0000

Spinnaker Release 1.0.0

Mon, 05 Jun 2017 11:21:34 -0400

Initial release

Administrator functionality

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

In Spinnaker, it is possible to define that users belonging to a certain role are considered “Administrators”. This virtually removes all READ/WRITE restrictions to accounts and applications for these users.

This feature gives admins an immense amount of power. Proceed with caution.

Enable and Configure Admin functionality

Manually add configuration in Fiat

In the fiat-local.yml config file, add the following:

fiat:
  admin:
    roles:
      - devops-admin

Alibaba Cloud Container Service for Kubernetes (ACK) Setup

Mon, 01 Jan 0001 00:00:00 +0000

This page describes how to set up a Kubernetes cluster on ACK to be used with Spinnaker’s Kubernetes provider.

Create a cluster

You can create a Kubernetes cluster on ACK using console as shown in the official documentation . You can also use Alibaba Cloud CLI or Terraform tools to automate provisioning your clusters.

Download kubectl configuration file on hal node

Run the following command on the hal node:

mkdir $HOME/.kube
scp root@$MASTER:/etc/kubernetes/kube.conf $HOME/.kube/config

Next Steps

Follow the setup instructions for adding a Kubernetes account in Spinnaker .

Amazon AWS Pub/Sub

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker pipelines can be triggered from a queue in Amazon Simple Queue Service (SQS) that receives new notifications from Amazon Simple Notification Service (SNS) .

Prerequisites

You need an AWS Account and the AWS Command Line Interface (cli) installed locally and configured with credentials that allow you to manage your AWS cloud resources.

Use the AWS Command Line tool or the AWS Console website to create a SNS Topic that will receive the messages destined for the queue and Spinnaker. You can do this by running the following commands:

Amazon EC2

Mon, 01 Jan 0001 00:00:00 +0000

An older doc is available that has some information around installing spinnaker but is no longer recommended nor supported AWS tutorial: Continuous Delivery using Spinnaker on Amazon EKS .

The AWS EC2 Provider allows you to deploy AWS EC2 resources with Spinnaker. The most common use case is the creation of AMIs and deploying the AMI’s to new autoscaling groups and then deleting the previous autoscaling groups.

Refer to the AWS Cloud Provider Overview to understand how AWS IAM must be set up with the Spinnaker AWS EC2 provider. It’s recommended to use node/pod roles to access AWS services and resources securely.

Amazon ECS

Mon, 01 Jan 0001 00:00:00 +0000

Resource mapping

Server group

A Spinnaker server group maps to an Amazon ECS service .

There are two ways to specify server group settings for Amazon ECS:

Inputs (default): Specify the container image, resource limits, and other settings needed to create an Amazon ECS task definition and service directly in the server group. This option supports deploying one container per Amazon ECS task (equivalent to a Spinnaker “instance”).
Artifact (supported as of 1.15.0): Specify a pipeline artifact to use as an Amazon ECS task definition for the service. The artifact should be a JSON file in the format of an Amazon ECS Register Task Definiton request . This option also requires that you specify containerName:imageDescription mappings for each image in your pipeline that you want to be deployed within the service. You can deploy multiple containers (up to 10) per Amazon ECS task using this option.

Amazon ECS

Mon, 01 Jan 0001 00:00:00 +0000

In the Amazon ECS cloud provider, an Account maps to a Spinnaker AWS account, which itself is able to authenticate against a given AWS account .

Prerequisites

Amazon ECS cluster

You need to create an Amazon ECS cluster . If using the ‘EC2’ launch type, this cluster must have enough EC2 instance capacity in it to deploy your containers. If using the ‘Fargate’ launch type, you don’t need to add any capacity to this cluster.

Amazon Web Services

Mon, 01 Jan 0001 00:00:00 +0000

Reference documentation coming soon!

See setup here

Annotation-Driven UI

Mon, 01 Jan 0001 00:00:00 +0000

This guide describes how to surface information about your Kubernetes resources in Deck’s details panel using Kubernetes annotations. These annotations can be text or HTML and can include templated values that are populated when the annotation is rendered by the browser.

Example Usage

Here’s a quick example of usage that will add a “Pod Info” section to the details panel for a pod:

kubectl annotate pod my-prod-pod-v000 \
  pod-info.details.html.spinnaker.io="<a href='https://internal-elk.net/{{"{{ name "}}}}'>Internal Logs Service</a>"

Here’s how this annotation will render in Spinnaker’s UI:

App Engine: Source to Prod

Mon, 01 Jan 0001 00:00:00 +0000

This tutorial is deprecated and no longer supported, but left for reference. Halyard is no longer supported or maintained

Overview

This codelab provides an overview of Spinnaker’s integration with App Engine. You’ll build and run a simple App Engine deployment pipeline with the following steps:

Prerequisites

Be sure you have your Google Cloud Platform project’s ID. This value will be referenced as GCP-PROJECT-ID below.
Be sure you have gcloud installed, and that it is authenticated with your GCP project. In most cases, this should only require running gcloud auth login <your@email.com> and following the instructions in the prompt. If you don’t have gcloud installed locally, you can always run gcloud from inside Cloud Shell, which you can open from your GCP console.
Be sure you have the App Engine Admin and Compute Engine APIs enabled for your GCP project:

gcloud services enable appengine.googleapis.com
gcloud services enable compute.googleapis.com

If this is your first time deploying to App Engine in your project, execute the following command to create an App Engine application. You cannot change the region, so choose wisely: gcloud app create --region <e.g., us-central>.

Configuration & installation

We’re going to trigger our Spinnaker pipelines using Github webhooks. In order to do so, we will have to expose Spinnaker’s API gateway to external traffic. If you are going to use this installation beyond this codelab, you should follow the guides for securing Spinnaker.

Artifacts from Build Triggers

Mon, 01 Jan 0001 00:00:00 +0000

Overview

When an external CI system triggers a pipeline, Spinnaker can use the CI build information to inject relevant artifacts into the pipeline. The instructions here assume that you have set up a CI system and are familiar with using property files to pass variables from CI builds to Spinnaker pipelines.

The extraction of artifacts from the build information is done via a Jinja template; the template uses the trigger as context and outputs a list of artifacts to inject into the pipeline. Spinnaker provides a set of standard templates to use for artifact extraction, which users can augment with custom templates.

Artifacts from Build Triggers

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Artifacts In App Engine

Mon, 01 Jan 0001 00:00:00 +0000

Artifacts can be used for the following in the Google App Engine provider:

They can be used to reference a GCS bucket that contains source code to be deployed on Google App Engine.
They can be used to reference a docker image stored in Google Container Registry to be deployed on App Engine Flex.
They can be used to reference config files (such as app.yaml) to be used during deployment to App Engine.

Artifacts referencing source code from GCS

To use an artifact to reference source code that is stored in a GCS bucket, use the “GCS” Source Type when configuring a Server Group.

Artifacts In App Engine (Legacy)

Mon, 01 Jan 0001 00:00:00 +0000

Artifacts can be used for several things in the Google App Engine provider:

They can be used to reference a GCS bucket that contains source code to be deployed on Google App Engine.
They can be used to reference a docker image stored in Google Container Registry to be deployed on App Engine Flex.
They can be used to reference config files (such as app.yaml) to be used during deployment to App Engine.

Artifacts Referencing Source Code From GCS

To use an artifact to reference source code that is stored in a GCS bucket, use the “GCS” Source Type when configuring a Server Group.

Artifacts In Cloud Foundry

Mon, 01 Jan 0001 00:00:00 +0000

Artifacts referencing app manifest

To use an artifact to reference a manifest file (such as a manifest stored in a GitHub repository), choose “Artifact from execution context” in the Application section of the “Configure Deployment Cluster” screen, and configure the artifact details.

In a Deploy stage, choose a GitHub file artifact as the manifest source for a server group.

Artifacts In Kubernetes

Mon, 01 Jan 0001 00:00:00 +0000

Manifests as artifacts

There are two ways to deploy a manifest:

The manifest is supplied statically to a pipeline as text
The manifest is supplied as an artifact

The image below shows a deploy stage that deploys a manifest stored in a GCS bucket:

Depending on how this pipeline is configured, it will only run when the referenced file in GCS is modified.

Artifacts In Kubernetes (Legacy)

Mon, 01 Jan 0001 00:00:00 +0000

Artifacts play an important role in the Kubernetes provider. Everything from the manifests you deploy, to the Docker images or ConfigMaps they reference can be expressed or deployed in terms of artifacts.

Manifests as artifacts

There are two ways to deploy a manifest:

The manifest is supplied statically to a pipeline as text
The manifest is supplied as an artifact

The image below shows a deploy stage that deploys a manifest stored in a GCS bucket:

Artifacts In Pipelines (Legacy)

Mon, 01 Jan 0001 00:00:00 +0000

Much of the behavior described here depends on looking up execution history in Redis. Deleting recent executions from Redis can cause unexpected behavior.

Now that you have an idea of what an artifact is in Spinnaker, you need to understand how it’s used within pipelines. An artifact arrives in a pipeline execution either from an external trigger (for example, a Docker image pushed to a registry) or by getting fetched by a stage. That artifact is then consumed by downstream stages based on pre-defined behavior.

Authentication Architecture

Mon, 01 Jan 0001 00:00:00 +0000

Authentication

There are three basic players in Spinnaker’s authentication workflow:

graph LR classDef default fill:#d8e8ec,stroke:#7a8288; linkStyle default stroke:#7a8288, stroke-width:2px, fill:none; gate(Gate) idp(IdentityProvider) deck(Deck/Browser) deck-->gate gate-->deck deck-->idp idp-->deck

Deck: Spinnaker’s UI. Consists of a set of static HTML, JavaScript, and CSS files. Generally served from an Apache server, but there is nothing special about Apache that makes Deck work. Replace with your favorite HTTP(S) server if you’d like.
Gate: Spinnaker’s API Gateway. All traffic (including traffic generated from Deck) flows through Gate. It is the point at which authentication is confirmed and one point (of several) where authorization is enforced.

Authorization Architecture

Mon, 01 Jan 0001 00:00:00 +0000

Ingress

Ingress involves the following components:

Clouddriver.
Front50 to query apps and service accounts.
Gate signs users in with externally provided roles (e.g. OpenID Connect, SAML). These roles are then merged with provider sourced roles (if any), tagged with the EXTERNAL source, and cached in Redis.
Igor gets the list of build systems and roles required to access them.

Egress

Egress involves the following components:

Redis stores computed roles, default permissions, and roles from external systems.
Clouddriver gets known accounts.
Front50 gets known apps.

Scaling

Fiat can be scaled by adding replicas. fiat.writeMode.enabled dictates if the Fiat instance will try to sync roles. Fiat instances coordinate around locks (in Redis) to ensure that only one instance synchronizes roles at a time.

Configure Automated Rollbacks in the Kubernetes Provider

Mon, 01 Jan 0001 00:00:00 +0000

There are clear benefits to having your stored manifests (in Git, GCS, etc…) match as closely as possible to what’s running in your cluster: you have auditability, versioned changes, and a high confidence in what code you have running. However, in some cases, pushing changes from someplace like GitHub through your build system all the way to production can simply take too long, and an escape hatch is needed when something has gone seriously wrong. Automated rollback is that escape hatch.

AWS CodeBuild

Mon, 01 Jan 0001 00:00:00 +0000

Setting up AWS CodeBuild as a Continuous Integration (CI) system within Spinnaker allows you to:

trigger pipelines when an AWS CodeBuild build changes its phase or state
add an AWS CodeBuild stage to your pipeline

The AWS Codebuild stage requires Spinnaker 1.19 or later.

Prerequisites

AWS CodeBuild project

You need to have an AWS CodeBuild project. To create a project, follow the instructions on how to create a CodeBuild service role (AWS CLI) .

Amazon Web Services Concepts

Mon, 01 Jan 0001 00:00:00 +0000

Concepts

There are two types of Accounts in the Spinnaker AWS provider:

AWS Managing account
AWS Managed account(s).

Note The AWS IAM structure must be set up prior to adding the accounts to spinnaker.

From the AWS perspective, AWS Managing account assumes control of the AWS Managed account(s) through the use of AWS IAM Roles. By assuming a role across AWS Accounts, Spinnaker can control AWS resources from multiple AWS Managed accounts.

Azure

Mon, 01 Jan 0001 00:00:00 +0000

If you are not familiar with Azure or any of the terms used below, please consult the Azure reference documentation .

Resource mapping

Account

In Azure (AZ), an Account maps to a credential able to authenticate against a given Azure (AZ) project - see the setup guide .

Load Balancer

A Spinnaker load balancer maps to an Azure Application Gateway .

Server Group

A Spinnaker server group maps to an Azure Virtual Machine Scale Set .

Instance

A Spinnaker instance maps to an Azure Virtual Machine Instance .

Azure

Mon, 01 Jan 0001 00:00:00 +0000

In Azure , an Account maps to a credential able to authenticate against a given Azure subscription .

Prerequisites

You need a Service Principal to authenticate with Azure and a Key Vault to store a default username/ssh public key for deployed VM Scale Sets . The next steps assume the use of the Azure CLI 2.0 . The example commands will set environment variables along the way for use when creating an account in the final stage. You can check that you have az installed by running:

Azure

Mon, 01 Jan 0001 00:00:00 +0000

This page instructs you on how to obtain an OAuth 2.0 client ID and client secret for use with your Microsoft Azure tenant. More extensive documentation is available on Microsoft’s site .

Setting up an Azure Application Registration

Navigate to https://portal.azure.com and log in with your Azure credentials.
On the left hand navigation pane, click “Azure Active Directory” –> “App registrations”.
Click “New application registration”, and fill in the details:
- Name of the application: (eg Spinnaker),
- Application type: Web app / API
- Sign-on URL: https://localhost:8084/login/oauth2/code/azure (replace localhost with your Gate address if known, and https with http if appropriate). For Spinnaker below v2025.2.0, it should be just https://localhost:8084/login
- Click “Create”
Note the “Application ID”, this is the client ID. Copy it to a safe place.
Click “Settings” -> “Keys”. Under “Passwords”, add a Key Description (eg Spinnaker), set the expiry and then click “Save”. “Value” will now be populated. This is your client secret; copy it to a safe place.

Configure Gate

Current configurations

Add the following to gate-local.yml. Note the Tenant ID of your organization is required for Azure OAuth 2.0 login. To obtain it:

Azure VM Scale Sets: Source to Prod

Mon, 01 Jan 0001 00:00:00 +0000

In this codelab, you will create a source-to-prod continuous delivery pipeline for a simple java based application targeting VM Scale Sets in Azure.

After completing this lab the following workflow will happen:

A developer pushes a commit to Github
Jenkins automatically builds a Debian package and pushes it to an Aptly repository
Spinnaker bakes the new package into an image
Spinnaker deploys to a test environment and disables the previous deployment
Spinnaker waits for a manual judgement of the test environment
Spinnaker deploys the image to the production environment and disables the previous deployment.

This codelab will walk through the following steps to implement this scenario:

Backend Service Extension Points

Mon, 01 Jan 0001 00:00:00 +0000

Project Setup

To enable plugins for a service, you only need to do two things:

Add implementation("com.netflix.spinnaker.kork:kork-plugins") to your {service}-core module.
Add @Import(PluginsAutoConfiguration::class) on your Main class or somewhere that will always be loaded.

Once the plugin framework is installed, you must create an API module to home your service extension points.

API Module

Plugins are all about the API. Ensure your project has a {service}-api module (called “the API module” from now on). The API module MUST NOT have other project module dependencies: Your {service}-core module (called the “core service module”) will actually depend on the API module, as it is the core’s and other modules’ responsibility to marshal between internal data structures and objects and the external API contracts.

Bake and Deploy Pipeline

Mon, 01 Jan 0001 00:00:00 +0000

VM only: This codelab requires you have a VM (for example, on AWS or GCP) on which to run it.

For Kubernetes, try Kubernetes Source-to-Prod ,

To walk you through some of the basics with Spinnaker, you’re going to set up a Spinnaker pipeline that bakes a virtual machine (VM) image containing redis, then deploys that image to a test cluster.

Note here that the us-east-1a availability zone is currently full, so it will need to be deselected in the corresponding ‘region’ checkbox list for each of these steps.

Best Practices for the Kubernetes Provider

Mon, 01 Jan 0001 00:00:00 +0000

The Kubernetes provider enables a wide variety of ways to deploy your manifests into Kubernetes clusters. This page provides best-practices for doing so.

Deploy Docker images by digest

If your registry exposes image changes by digest , we recommend deploying images by their digest rather than tag, e.g. gcr.io/my-image@sha256:95ff090... rather than gcr.io/my-image:v1.

The digest is a content-addressable way to reference your image, because it’s derived from the hash of the image contents. If your manifest points to an image by its digest, you know that each time it’s deployed it points to the same contents (binary, dependencies, config, etc…). If you rely on the tag, deploying the same Manifest twice can have different results.

Triggering pipelines with Bitbucket Server

Mon, 01 Jan 0001 00:00:00 +0000

Overview of supported Bitbucket Server events

Spinnaker supports the following Bitbucket Server webhook events:

Declined (pr:declined)
Deleted (pr:deleted)
Merged (pr:merged)
Modified/Source branch updated (pr:from_ref_updated)
Opened (pr:opened)
Push (repo:refs_changed)

Before you begin

You are familiar with creating and triggering webhooks in Bitbucket Server.
You have configured Bitbucket notifications (webhooks) in Spinnaker and enabled the desired webhook events in your Bitbucket repository.

Add a Bitbucket webhook event as a pipeline trigger

In your pipeline, go to Configuration > Automated Triggers.

Bitbucket File

Mon, 01 Jan 0001 00:00:00 +0000

Bitbucket file artifacts are references to files stored in Bitbucket . They are generally consumed by stages that read configuration from text files, such as a Deploy Manifest stage.

Fields

Field	Explanation
`type`	Always `bitbucket/file`.
`reference`	The full path including filename for retrieval via the Bitbucket API. `https://api.bitbucket.org/2.0/repositories/$ORG/$REPO/src/$VERSION/$FILEPATH`. For more info, see the documentation here .
`name`	The file path within your repo. `path/to/file.yml` is an example.
`version`	N/A. Must be specified in reference.
`location`	N/A

Example

{
  "type": "bitbucket/file",
  "reference": "https://api.bitbucket.org/2.0/repositories/org/repo/src/master/manifests/config.yaml",
  "name": "manifests/config.yaml"
}

Bitbucket File

Mon, 01 Jan 0001 00:00:00 +0000

These artifacts are generally consumed by stages that read configuration from text files, such as a Deploy Manifest stage.

Bitbucket file artifact in the UI

The pipeline UI exposes the following fields for the Bitbucket file artifact:

Field	Explanation
Account	A Bitbucket artifact account.
File path	The full path (including filename) for retrieval via the Bitbucket API. Example: `https://api.bitbucket.org/2.0/repositories/$ORG/$REPO/src/$VERSION/$FILEPATH`.

In a trigger

When configuring certain triggers, you can use a Bitbucket file as an expected artifact.

Continuous Delivery to Kubernetes on Oracle

Mon, 01 Jan 0001 00:00:00 +0000

In this codelab you will configure a Spinnaker pipeline to deploy an application from Kubernetes manifest files targeting Kubernetes on Oracle Cloud Infrastructure Container Engine (OKE).

Prerequisites

Before we begin, we need to do the following:

Configure Kubernetes

If you don’t already have a cluster for this purpose, you can follow this tutorial until a Kubernetes cluster on OKE is created.

Create a compute instance

Create a compute instance on Oracle Cloud Infrastructure (OCI) to host Spinnaker by following these instructions . Spinnaker supports Ubuntu 18.04 or higher.

CI Features

Mon, 01 Jan 0001 00:00:00 +0000

One of the goals of Managed Delivery is to show you the journey of your code, from commit to deployment, in an easy, consistent way. In order to enable this experience, we created an integration between Managed Delivery and the Continuous Integration (CI) provider, which is described below.

Note: in order to take advantage of this feature, your Spinnaker operator/administrator will have to configure a CI provider which matches your company’s setup. They can look for available open-source or commercial Spinnaker CI providers, or even develop their own. See the developer guide on CI integration .

Cloud Foundry

Mon, 01 Jan 0001 00:00:00 +0000

If you are not familiar with Cloud Foundry (CF) or any of the terms used below, please consult Cloud Foundry’s reference documentation .

Resource mapping

Account

In CF, an Account maps to a user account on a CF foundation (where a foundation is a BOSH Director and all the VMs it deploys). This user account is provided via configuration to Spinnaker, and Spinnaker’s privileges are determined by the CF user account’s permissions; for example, Spinnaker can manage CF apps across all of the orgs and spaces which its CF user account can access.

Cloud Foundry

Mon, 01 Jan 0001 00:00:00 +0000

In Cloud Foundry (CF), an Account maps to a user account on a CF foundation (a BOSH Director and all the VMs it deploys). You can add multiple accounts for one or more CF foundations.

Prerequisites

Your CF foundations’ API endpoints must be reachable from your installation of Spinnaker.

Add an account

First, make sure that the provider is enabled and add an account named my-cf-account to the clouddriver list of Cloud Foundry accounts: in ~/spinnaker-kustomize/overlays/config/files/clouddriver-local.yml

Code Languages, Libraries, and Conventions

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker is a collection of microservices built from a common foundation which has evolved over time. You do not need to know all of the technologies listed to contribute. Please consider these standards and conventions when submitting pull requests to Spinnaker.

Languages

Spinnaker is comprised of JVM backend-services and a frontend application (Deck). See an overview of the architecture in our reference documentation.

Use the following languages to fix and extend Spinnaker services:

Code Of Conduct

Mon, 01 Jan 0001 00:00:00 +0000

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Contributor Covenant Code of Conduct

Our pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Commands

Mon, 01 Jan 0001 00:00:00 +0000

HALYARD IS DEPRECATED

Important

At this time, halyard is considered deprecated and no longer supported.
This document is kept here and alive for historical purposes. Documentation should all be moved to native configuration files, and for more questions and information please join the spinnaker slack.

hal

A tool for configuring, installing, and updating Spinnaker.

Component Sizing

Mon, 01 Jan 0001 00:00:00 +0000

HALYARD IS DEPRECATED

Important

Custom sizing can be specified for each Spinnaker component within the Halyard configuration. You can either add these sizes to the Halyard config manually, or use any of the Halyard component sizing commands . This feature is currently only supported for distributed deployments using Kubernetes (hal config deploy edit --type distributed --account-name my-k8s-cluster).

Configure a Git Repo Artifact Account

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Each time a pipeline needs a Git repo artifact during execution, Clouddriver clones the entire repo, sends the repo artifact to the pipeline, and then deletes the cloned repo immediately.

Spinnaker includes a feature for caching a Git repo artifact. Clouddriver clones the Git repo the first time a pipeline needs it and then caches the repo for a configured retention time. Each subsequent time the pipeline needs to use that Git repo artifact, Clouddriver does a git pull to fetch updates rather than cloning the entire repo again. This behavior is especially useful if you have large repositories. Clouddriver deletes the cloned Git repo when the configured retention time expires.
This is an opt-in feature that is disabled by default. See the Enable git pull support section for details.

Configure a GitHub artifact account

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

You need a GitHub account.

Download credentials

Start by generating an access token for GitHub. The token requires the repo scope.

Add the credentials either to a secrets manager for use by reference or to a volume mounted into the clouddriver pods by modifying the deployment.yaml for clouddriver.

Add the account and enable it

Add the below to clouddriver-local.yml to enable artifacts and add a github account

artifacts:
  enabled: true
  github:
    enabled: true
    accounts:
    - name: my-github-account
      tokenFile: /mnt/some/file|secretReference

There are more options available if you look at the github account definition code

Configure a GitLab artifact account

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

You need a GitLab account.

Download credentials

Start by generating an access token for GitLab.

Add the credentials either to a secrets manager for use by reference or to a volume mounted into the clouddriver pods by modifying the deployment.yaml for clouddriver.

Add the account and enable it

All that’s required are the following configuration:

artifacts:
  enabled: true
  gitlab:
    enabled: true
    accounts:
    - name: my-gitlab-account
      token: patToken
      tokenFile: /mnt/someplace/tokenFile

There are more options including URL restrictions that can be set to allow only internal gitlab hosts. See the gitlab account definition for information.

Configure Bitbucket Artifact Credentials

Mon, 01 Jan 0001 00:00:00 +0000

If the files are hidden behind basic auth, you can configure an artifact account with the needed credentials to read your artifact.

Download credentials

Collect your basic auth $USERNAME and $PASSWORD
Pick a $USERNAME_PASSWORD_FILE location on your disk

Run:

echo ${USERNAME}:${PASSWORD} > $USERNAME_PASSWORD_FILE

Add the credentials either to a secrets manager for use by reference or to a volume mounted into the clouddriver pods by modifying the deployment.yaml for clouddriver.

Add the account and enable it

Enable the Bitbucket artifact provider in clouddriver-local.yml and add an artifact account:

Configure Helm Artifact account

Mon, 01 Jan 0001 00:00:00 +0000

The provider can be an Artifactory like Nexus , JFrog , or Chartmuseum .

If the files are hidden behind basic auth, you can configure an artifact account with the needed credentials to read your artifacts. Basic auth is the only authentication mechanism supported for accessing a Helm artifact account.

Setup usage in pipeline executions

Download credentials

Collect your basic auth $USERNAME and $PASSWORD
Pick a $USERNAME_PASSWORD_FILE location on your disk

Run:

echo ${USERNAME}:${PASSWORD} > $USERNAME_PASSWORD_FILE

Add the credentials either to a secrets manager for use by reference or to a volume mounted into the clouddriver pods by modifying the deployment.yaml for clouddriver.

Configure HTTP Artifact Credentials

Mon, 01 Jan 0001 00:00:00 +0000

If the files are hidden behind basic auth, you can configure an artifact account with the needed credentials to read your artifact. If not, no further configuration is needed, Spinnaker can automatically add a no-auth-http-account for this purpose.

You can configure more than one artifact account, each with separate credentials. Specify which account to use in the configuration for the stage that reads the data. If you have only one such account configured, the stage config for this is hidden, and the single account is automatically used.

Configure Maven Artifact Credentials

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker can be configured to deploy artifacts stored in a Maven repository.

You can configure more than one artifact account, each with separate credentials. Specify which account to use in the configuration for the stage that reads the data.

Download credentials

Maven accounts at this time do not support credential authorization. We’d welcome PRs to enable this and get maven closer to full artifact support.

Add the account and enable it

artifacts:
  enabled: true
  maven:
    enabled: true
    accounts:
    - name:  nexus-internal
      repositoryUrl: https://my.repo.example.com

Configure S3 Artifact

Mon, 01 Jan 0001 00:00:00 +0000

All that’s required are the following values:

API_ENDPOINT=
API_REGION=
REGION=
ARTIFACT_ACCOUNT_NAME=my-s3-account

Download credentials

Create a user with an accessKey or secretKey. Otherwise, spinnaker will use the credentials of the clouddriver pod to attempt to access the s3 resource.

Add the accesskey and secret key either to a secrets manager for use by reference or to a volume mounted into the clouddriver pods by modifying the deployment.yaml for clouddriver.

Add the account and enable it

Add the following to clouddriver-local.yml

Configure Spinnaker's Usage of Redis

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker relies on its cache for a few key purposes:

Session data for logins
Bake logs and history
Recording which triggers have already been acted upon when using docker/jenkins triggers
ETC.

Most of these can be configured to your needs, whether it is to make Spinnaker more responsive, or reduce the load on a downstream dependency. Some of these settings apply only to SQL or REDIS depending upon configuration. The below are some examples of adjusting these configurations.

Configuring GCS Artifact Credentials

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker stages that read data from artifacts can consume GCS objects as artifacts.

Prerequisites

You need a Google Cloud Platform (GCP) project to host a bucket in. The next steps assume you’ve already created a project , and installed gcloud . You can check that gcloud is installed and authenticated by running:

gcloud info

Download credentials

Spinnaker needs a service account to authenticate as against GCP, with the roles/storage.admin role enabled. If you don’t already have such a service account with the corresponding JSON key downloaded, you can run the following commands to do so:

Configuring Oracle Object Storage Artifact Credentials

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker stages that read data from artifacts can consume Oracle Object Storage objects as artifacts.

Download credentials

If you have enabled Oracle Cloud provider in Spinnaker, you may use the same region, Tenancy’s OCID, user’s OCID, private key file, and fingerprint to enable Oracle Object Storage Artifact. You will need the following to enable Oracle Object Storage Artifact in Spinnaker:

A user in IAM for the person or system who will be using Spinnaker, and that user must be granted access to Object Storage or in one IAM group with permissions of Object Storage.

Custom Settings

Mon, 01 Jan 0001 00:00:00 +0000

HALYARD IS DEPRECATED

Important

Furthermore, some users will be more comfortable forgoing Halyard’s configuration generation, or will want to port their old Spinnaker configuration into Halyard. For these users & use-cases, Halyard supports custom Profiles , and custom Service Settings .

DC/OS: Source to Prod

Mon, 01 Jan 0001 00:00:00 +0000

0. Setup

Prerequisites

Github repository with the source code to deploy
Enterprise DC/OS cluster (1.8 or greater)
- Marathon-lb is should be installed and running
- For the examples in this codelab we’ll say that it’s at https://dcos.example.com so you should replace that with the URL to your cluster
Jenkins instance
- This can be installed on your DC/OS cluster as a Mesosphere Universe package

Configure Spinnaker

clouddriver-local.yml

dcos:
  enabled: true
  clusters:
    - name: codelab-cluster
      dcosUrl: https://dcos.example.com
      insecureSkipTlsVerify: true
  accounts:
    - name: codelab-dcos-account
      dockerRegistries:
        - accountName: my-docker-registry
      clusters:  
        - name: codelab-cluster
          uid: ${DCOS_USER}
          password: ${DCOS_PASSWORD}
dockerRegistry:
  enabled: true
  accounts:
  - name: my-docker-registry
    address: https://index.docker.io
    repositories:
    - lwander/spin-kub-demo
    username: ${DOCKER_USER}
    password: ${DOCKER_PASSWORD}

Enable Docker

Configure a docker registry

Debian Package

Mon, 01 Jan 0001 00:00:00 +0000

These artifacts are generally consumed by the Bake stage.

HTTP file artifact in the UI

The pipeline UI exposes the following fields for the Debian Package artifact:

	Explanation
Account	An HTTP artifact account.
URL	The fully-qualified URL from which the file can be read.

In a trigger

When configuring certain triggers, like Pubsub you can use a custom artifact.

Configuring Debian Package fields in a pipeline trigger’s expected artifact settings.

Deploy Artifacts from Artifactory to CF

Mon, 01 Jan 0001 00:00:00 +0000

In this codelab, you will deploy an artifact to Cloud Foundry via a Spinnaker pipeline. The pipeline is triggered by an artifact published to a JFrog Artifactory Maven repository or by an app manifest stored in a GitHub repository.

Prerequisites

This codelab assumes you have the following:

Artifact support enabled .
An Artifactory repository configured to accept a Maven artifact—the JAR for your application
A GitHub repository containing a manifest with which to deploy your application

1. Add Artifactory Search to Spinnaker

a. Enable the Artifactory repository:

Deploy GCS Pub/Sub Artifacts to Google App Engine

Mon, 01 Jan 0001 00:00:00 +0000

The goal of this codelab is to trigger a Spinnaker pipeline with a Pub/Sub message from GCS upon upload of a tarball.

In this codelab, you will deploy artifacts to Google App Engine (GAE) via a Spinnaker pipeline. The pipeline is configured to trigger on Pub/Sub messages from a GCS bucket serving as an artifact repository. The Pub/Sub messages contain context that allows Spinnaker to parse and deploy the stored artifacts.

Deploy GCS Pub/Sub Artifacts to Cloud Foundry

Mon, 01 Jan 0001 00:00:00 +0000

In this codelab, you will deploy an artifact to Cloud Foundry via a Spinnaker pipeline that is triggered by JAR uploads to a Google Cloud Storage (GCS) bucket.

Prerequisites

This codelab assumes you have the following:

A billing-enabled Google Cloud Platform (GCP) project.
The gcloud CLI tool (installed locally on your computer).
Artifact support enabled .

1. Create a GCS Bucket for Artifact Storage

a. Log in with gcloud:

$ gcloud auth login

b. Run the gsutil mb command to create a bucket within your GCP project, giving your project’s ID (PROJECT_ID below) and the name of the bucket to create (BUCKET):

Deploy Helm Charts

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker surfaces a Bake (Manifest) stage to turn templates into manifests with the help of a templating engine. Helm relies on the helm template command. For more details, see helm template --help.

>This stage is intended to help you package and deploy applications that you own, one that are actively developing and redeploying frequently. It is not intended to serve as a one-time installation method for third-party packages. If that is your goal, it's better to call `helm install` once when bootstrapping your Kubernetes cluster. Make sure that you have configured [artifact support](/docs/setup/other_config/artifacts/) in Spinnaker first. All Helm charts are fetched/stored as artifacts in Spinnaker. Read more in the [reference pages](/docs/reference/artifacts).

Configure the Bake (Manifest) stage

When configuring the Bake (Manifest) stage using a Helm (Helm 2 or Helm 3) render engine, you can specify the following:

Deploy Kubernetes Manifests

Mon, 01 Jan 0001 00:00:00 +0000

This guide shows the basics of how to deploy a Kubernetes manifest using the Kubernetes provider .

There are two main steps:

Specify which manifest to deploy

This is required.
Override artifacts in the manifest

Optionally, you can override some artifacts (as fields) at run time (for example, which Docker image to use.)

Specify your manifest

Depending on your needs, there is more than one way to specify the manifest that you want to deploy:

Docker Image

Mon, 01 Jan 0001 00:00:00 +0000

A Docker image is a snapshot of a container, to be run locally, or in the cloud. Docker image artifacts are used as references to images in registries , such as GCR , or Docker Hub . The artifacts can be deployed to Kubernetes or App Engine, and generally trigger pipelines from notifications sent by their registry.

Fields

Field	Explanation
`type`	Always `docker/image`.
`reference`	The fully-qualified image name, including version and registry. This can be done either by tag (`gcr.io/project/my-image:v1.2`) or image digest `gcr.io/project/my-image@sha256:28f82eba`.
`name`	The image’s name (typically the registry and repository) without the image’s version. `gcr.io/project/my-image` is an example.
`version`	The image’s tag or digest.
`location`	N/A

Example

{
  "type": "docker/image",
  "reference": "gcr.io/project/my-image@sha256:28f82eba",
  "name": "gcr.io/project/my-image",
  "version": "sha256:28f82eba"
}

Docker Image

Mon, 01 Jan 0001 00:00:00 +0000

The artifacts can be deployed to Kubernetes or App Engine, and generally trigger pipelines from notifications sent by their registry.

Docker image artifact in the UI

The pipeline UI exposes the following fields for the Docker image artifact:

Field	Explanation
Account	A Docker registry artifact account.
Docker image	The name of the Docker image, including the registry and image repository.

In a trigger

When configuring the Docker Registry trigger, you can use a Docker image as an expected artifact.

Docker Registry

Mon, 01 Jan 0001 00:00:00 +0000

:warning: This only acts as a source of images, and does not include support for deploying Docker images.

When configuring Docker Registries, an Account maps to a credential able to authenticate against a certain set of Docker repositories .

Prerequisites

The Docker Registry you are configuring must already exist.
That Registry must support the v2 registry API . OCI registries are ALSO supported at this time.

Registry providers

You can set up a Docker Registry provider for Spinnaker using any of the repositories listed here. Each one supports the same API, but there are subtle differences in how to get them to work with Spinnaker.

Documentation Style Guide

Mon, 01 Jan 0001 00:00:00 +0000

This page gives writing style guidelines for the Spinnaker documentation. Since these are guidelines, not rules, use your best judgment when creating content. Feel free to propose changes to this document in a pull request.

If you have a style question that isn’t answered in this guide, ask the SIG Docs team in the Spinnaker Slack #sig-documentation channel.

Language

The Spinnaker documentation uses U.S. English spelling and grammar. However, use the international standard for putting punctuation outside of quotation marks.

Set up the Kubernetes provider for Amazon EKS

Mon, 01 Jan 0001 00:00:00 +0000

Before you proceed further with this setup, we strongly recommend that you familiarize yourself with Amazon EKS concepts . Also, visit the AWS global infrastructure region table for the most up-to-date information on Amazon EKS regional availability.

These instructions assume that you have AWS CLI installed and configured on an Ubuntu machine running on AWS EC2.

Preparing to install Spinnaker on EKS

The following steps describes how to the tools you need to install and manage Spinnaker and EKS.

Embedded base64

Mon, 01 Jan 0001 00:00:00 +0000

Rather than refer to a resource by URI, you can embed the artifact’s contents directly into the "reference" field in base64.

Fields

Field	Explanation
`type`	Always `embedded/base64`.
`reference`	The base64 encoded artifact contents.
`name`	An optional human-readable identifier.

Example

{
  "type": "embedded/base64",
  "reference": "dmFsdWU6IDEKZm9vOiBiYXIK",
  "name": "my-properties-file",
}

Embedded Base64

Mon, 01 Jan 0001 00:00:00 +0000

Embedded Base64 artifact in the UI

The pipeline UI exposes the following fields for the embedded Base64 artifact:

Field	Explanation
Account	Always "embedded-artifact".
Name	A human-readable identifier for the artifact.
Contents	The Base64-encoded contents of the artifact.

In a trigger

When configuring a trigger, you can (for example) configure an embedded Base64 default artifact.

Providing an embedded Base64 default artifact for a trigger’s expected artifact.

Externalize Redis

Mon, 01 Jan 0001 00:00:00 +0000

One of the easiest ways to improve Spinnaker’s reliability at scale is to use an external Redis. The default redis component isn’t configured to be production-ready. If you have a hosted Redis alternative, or a database team managing a Redis installation, we highly recommend using that.

Configure a Spinnaker-wide Redis

First, determine the URL of your Redis installation. Some examples include:

redis://some.redis.url:6379: Redis running at some.redis.url on port 6379.
redis://admin:passw0rd@some.redis.url:6379: Same as above, but with a username/password pair.

Fiat Permissions

Mon, 01 Jan 0001 00:00:00 +0000

Unless you have set fiat.legacyFallback to true (defaults to false) you will need to configure Igor CI services with Fiat READ and WRITE permissions.

Here is a Jenkins example:

jenkins:
  enabled: true
  masters:
  - name: <jenkins master name>
    address: http://<jenkins ip>/jenkins
    username: <jenkins admin user>
    password: <admin password>
    csrf: true
    permissions:
      READ:
      - foo
      - bar
      WRITE:
      - bar

In the example above, users with the foo or bar roles will be able to see the build master and use it as a trigger, and users with the bar role will additionally be able to trigger builds.

Frontend Plugin Development

Mon, 01 Jan 0001 00:00:00 +0000

Overview of Frontend plugins

Frontend plugins provide a way to change the behavior of Deck, Spinnaker’s UI service. You can add configuration and validation for new stages provided by Orca plugins, override existing components with your own implementation, or add new Kubernetes kind definitions for custom resources in your environment. Spinnaker loads plugins at runtime through Gate.

You can write plugins in any JavaScript-compatible language, but the development tooling is designed for JavaScript and TypeScript.

G Suite

Mon, 01 Jan 0001 00:00:00 +0000

This page instructs you on how to obtain an OAuth 2.0 client ID and client secret for use with your G Suite organization (previously known as Google Apps for Work).

Get client ID and secret

Navigate to https://console.developers.google.com/apis/credentials .
Click “Create credentials” –> OAuth client ID.
Select “Web Application”, and enter a name.
Under “Authorized redirect URIs”, add https://localhost:8084/login/oauth2/code/google (For Spinnaker below v2025.2.0, it should be https://localhost:8084/login), replacing domain with your Gate address, if known, and https with http if appropriate. Click Create.
Note the generated client ID and client secret. Copy these to a safe place.

GCE Source To Prod

Mon, 01 Jan 0001 00:00:00 +0000

In this codelab, you create a cohesive workflow which takes source code and builds, tests and promotes it to production. You can also watch a video of this codelab in this Youtube playlist .

This will be accomplished via 3 pipelines:

Bake & Deploy to Test
Validate Test
Promote to Prod

You will be using a custom-built image that includes sample application source code, a Jenkins instance, a Debian repository (aptly) and a Spinnaker instance.

GCS Object

Mon, 01 Jan 0001 00:00:00 +0000

GCS is an object store, and GCS object artifacts are references to objects stored in GCS buckets. These artifacts are generally consumed by stages that read configuration from text files, such as a Deploy Manifest or App Engine Deploy stage.

Fields

Field	Explanation
`type`	Always `gcs/object`.
`reference`	The `gs://`-prefixed reference to your file. May be suffixed with the object’s version . `gs://bucket/file.yml#1360383693620000` is an example.
`name`	The same as `reference`, but never with a version.
`version`	The object’s version , if applicable.
`location`	N/A

Example

{
  "type": "gcs/object",
  "reference": "gs://bucket/file.yml#1360383693620000",
  "name": "gs://bucket/file.yml",
  "version": "1360383693620000"
}

GCS Object

Mon, 01 Jan 0001 00:00:00 +0000

These artifacts are generally consumed by stages that read configuration from text files, such as a Deploy Manifest or App Engine Deploy stage.

GCS object artifact in the UI

The pipeline UI exposes the following fields for the GCS object artifact:

Field	Explanation
Account	A GCS artifact account.
Object path	The path to the artifact file, beginning with `gs://`.

In a trigger

When configuring certain triggers (such as a Pub/Sub trigger with Pub/Sub System Type “Google”), you can use a GCS object as an expected artifact.

Git Repo

Mon, 01 Jan 0001 00:00:00 +0000

The Git Repo artifact is available in version 1.17 or later.

Git Repo artifacts are references to Git repositories that are hosted by a Git hosting service. They are consumed by stages that need multiple files to produce an output such as the Bake (Manifest) stage when using the Kustomize template renderer. Unlike other artifact implementation, the Git Repo artifact will work with any Git hosting service as long as the repository can be cloned using the Git CLI.

Git Repo

Mon, 01 Jan 0001 00:00:00 +0000

The Git Repo artifact is available in version 1.17 or later.

They are consumed by stages that need multiple files to produce an output, such as the Bake (Manifest) stage when using the Kustomize template renderer. Unlike other artifact implementations, the Git Repo artifact works with any Git hosting service as long as the repository can be cloned using the Git CLI.

Git Repo artifact in the UI

The pipeline UI exposes the following fields for the Git Repo artifact:

GitHub File

Mon, 01 Jan 0001 00:00:00 +0000

GitHub file artifacts are references to files stored in GitHub or GitHub Enterprise . They are generally consumed by stages that read configuration from text files, such as a Deploy Manifest stage.

Fields

Field	Explanation
`type`	Always `github/file`.
`reference`	The full path including filename for retrieval via the GitHub API. This is the `contents_url` as referenced by a PushEvent . `https://api.github.com/repos/baxterthehacker/public-repo/contents/path/to/file.yml` is an example for public GitHub. `https://github.mydomain.com/api/v3/repos/orgname/reponame/contents/path/to/file.yml` is an example for GHE.
`name`	The file path within your repo. `path/to/file.yml` is an example.
`version`	The file’s commit, branch, or tag.
`location`	N/A

Example

{
  "type": "github/file",
  "reference": "https://api.github.com/repos/baxterthehacker/public-repo/contents/path/to/file.yml",
  "name": "path/to/file.yml",
  "version": "aec855f4e0e11"
}

GitHub File

Mon, 01 Jan 0001 00:00:00 +0000

These artifacts are generally consumed by stages that read configuration from text files, such as a “Deploy (Manifest)” stage.

GitHub file artifact in the UI

The pipeline UI exposes the following fields for the GitHub file artifact:

Field	Explanation
Account	A GitHub artifact account.
File path	The path to the artifact file, beginning at the root of the Git repository.
Content URL	The GitHub API content URL for the artifact file.
Commit/Branch	The commit hash or branch name to use when retrieving the artifact file from GitHub.

In a trigger

When configuring a Git trigger with Type “GitHub”, you can use a GitHub file as an expected artifact.

GitHub Organizations

Mon, 01 Jan 0001 00:00:00 +0000

WARNING

IF YOU ARE NOT CAREFUL you can configure spinnaker to allow ANY github user, not just the ones in your organization access to spinnaker. As such, please make sure to set the restrictions as appropriate for your org! Specifically spring.security.oauth2.client.registration.github.provider-requirements restriction to limit access to a specific github org! Failure to set this places your spinnaker installation at risk of unintended access! For this to work, your users MUST be public members to validate their membership in the github organization.

GitHub Teams

Mon, 01 Jan 0001 00:00:00 +0000

GitHub App Authentication (Recommended)

GitHub App authentication, available in releases after 2025.4.0, is the preferred method for connecting Spinnaker to GitHub. It offers significant advantages over Personal Access Tokens (PATs):

Higher Rate Limits: GitHub Apps have a rate limit of 15,000 requests per hour (vs 5,000 for PATs).
Enhanced Security: Uses short-lived tokens that are automatically refreshed, rather than long-lived static tokens.
Granular Permissions: Apps can be scoped to specific permissions.

Prerequisites

You have GitHub organization admin permissions to create and install the app.

1. Create a GitHub App

Navigate to your GitHub Organization Settings > Developer settings > GitHub Apps.
Click New GitHub App.
Set the following fields:
- GitHub App Name: e.g., spinnaker-fiat-auth.
- Homepage URL: Your Spinnaker URL (or placeholder).
- Callback URL: Your Spinnaker URL (or placeholder).
- Webhook: Uncheck “Active” (not needed for authorization).
Permissions:
- Organization Permissions > Members: Read-only
Click Create GitHub App.
Note the App ID.
Generate a Private key and save the .pem file.
Install App: Go to “Install App” in the sidebar and install it on your organization. Note the Installation ID from the URL (e.g., https://github.com/organizations/my-org/settings/installations/12345678 -> 12345678).
- Install at the organization level (not per-repo) so team membership lookups work for all repos.

GitHub App installation tokens are short-lived (1 hour) and Fiat caches them in memory with an early refresh buffer. They are never written to disk.
PATs configured with --accessToken are stored in Fiat configuration; rotate them periodically and handle them like any other long-lived secret.

Personal Access Token (Legacy)

If you cannot use a GitHub App, you can still use a Personal Access Token (PAT). Note that this has lower rate limits.

Gitlab File

Mon, 01 Jan 0001 00:00:00 +0000

Gitlab file artifacts are references to files stored in Gitlab . They are generally consumed by stages that read configuration from text files, such as a Deploy Manifest stage.

Fields

Field	Explanation
`type`	Always `gitlab/file`.
`reference`	The full path including filename for retrieval via the Gitlab API. `https://gitlab.example.com/api/v4/projects/13083/repository/files/manifests%2Fconfig%2Eyaml/raw` is an example from the Gitlab documentation. For more info, see the documentation here .
`name`	The file path within your repo. `path/to/file.yml` is an example.
`version`	The file’s commit or branch.
`location`	N/A

Example

{
  "type": "gitlab/file",
  "reference": "https://gitlab.example.com/api/v4/projects/13083/repository/files/manifests%2Fconfig%2Eyaml/raw",
  "name": "manifests/config.yaml",
  "version": "master"
}

GitLab File

Mon, 01 Jan 0001 00:00:00 +0000

These artifacts are generally consumed by stages that read configuration from text files, such as a Deploy Manifest stage.

GitLab file artifact in the UI

The pipeline UI exposes the following fields for the GitLab file artifact:

Field	Explanation
Account	A GitLab artifact account.
File path	The path to the artifact file, beginning at the root of the Git repository.
Commit/Branch	The commit hash or branch name to use when retrieving the artifact file from GitLab.

In a trigger

When configuring a Git trigger with Type “GitLab”, you can use a GitLab file as an expected artifact.

Google Kubernetes Engine (GKE) Setup

Mon, 01 Jan 0001 00:00:00 +0000

This page describes how to set up a Kubernetes cluster on GKE to be used with Spinnaker’s Kubernetes provider. The process is very simple, but you need to do some specific things to allow Spinnaker to authenticate against your cluster.

Note: To manage and create clusters in a given project, you need the roles/container.admin role as described here .

Create a cluster

If you don’t already have a cluster for this purpose, you can create a Kubernetes cluster on GKE using either gcloud or the the Cloud Console as shown in the official documentation . Third party tools like Terraform work too, and can be used to automate provisioning your clusters.

Google App Engine

Mon, 01 Jan 0001 00:00:00 +0000

If you are not familiar with App Engine or any of the terms used below, please consult App Engine’s reference documentation .

Resource mapping

Account

A Spinnaker account maps to a single App Engine application, a top-level resource that contains services, versions, and instances. Spinnaker authenticates itself with App Engine using service account credentials for a Google Cloud Platform project - see the setup guide .

Load Balancer

A Spinnaker load balancer maps to an App Engine service.

Google App Engine

Mon, 01 Jan 0001 00:00:00 +0000

In Google App Engine , an Account maps to a credential able to authenticate against a given Google Cloud Platform project.

Prerequisites

You need a Google Cloud Platform project to run Spinnaker against. The next steps assume you’ve already created a project , and installed gcloud . You can check that gcloud is installed and authenticated by running:

gcloud info

If this is your first time deploying to App Engine in your project, create an App Engine application. You cannot change your application’s region, so pick wisely:

Google Cloud Build

Mon, 01 Jan 0001 00:00:00 +0000

Setting up Google Cloud Build as a Continuous Integration (CI) system within Spinnaker allows you to:

trigger pipelines when a GCB build completes
add a GCB stage to your pipeline

Prerequisites

GCP project

You need to have a Google Cloud Platform project with the Cloud Build API enabled. You can enable the API with the following gcloud command:

gcloud services enable cloudbuild.googleapis.com

Pub/sub subscription

Google Cloud Build sends Build Notifications when the state of your build changes. Spinnaker subscribes to these pub/sub messages so that it can…

Google Cloud Pub/Sub

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker pipelines can be triggered using a Google Pub/Sub subscription .

Prerequisites

You need a Google Cloud Platform (GCP) project to with the Pub/Sub API enabled , and gcloud installed locally. You can check that gcloud is installed and authenticated by running:

gcloud info

A Pub/Sub subscription

The Pub/Sub integration can be used to either:

Start pipelines by sending Pub/Sub messages from a system you own.
Start pipelines using Pub/Sub messages originating from a Google Cloud system, such as Google Cloud Storage , or Google Container Registry .

Google Cloud Run

Mon, 01 Jan 0001 00:00:00 +0000

If you are not familiar with Cloud Run or any of the terms used below, please consult Cloud Run’s reference documentation .

Resource mapping

Account

A Spinnaker account maps to a single Cloud Run application, a top-level resource that contains services, versions, and instances. Spinnaker authenticates itself with Cloud Run using service account credentials for a Google Cloud Platform project - see the setup guide .

Load Balancer

A Spinnaker load balancer maps to an Cloud Run service.

Google Cloud Run

Mon, 01 Jan 0001 00:00:00 +0000

In Google Cloud Run , an Account maps to a credential able to authenticate against a given Google Cloud Platform project.

Prerequisites

gcloud info

To initialize the gcloud CLI, run the following command:

gcloud init

If this is your first time deploying to Cloud Run in your project, create a Cloud Run application.

Google Compute Engine

Mon, 01 Jan 0001 00:00:00 +0000

If you are not familiar with Google Compute Engine or any of the terms used below, please consult Compute Engine’s reference documentation .

Resource mapping

Account

In Google Compute Engine (GCE), an Account maps to a credential able to authenticate against a given Google Cloud Platform (GCP) project - see the setup guide .

Load Balancer

A Spinnaker load balancer maps to a GCE load balancer .

GCE supports many different types of load balancers, including: HTTPS(S), SSL Proxy, Network and Internal. Each of these is supported by Spinnaker.

Google Compute Engine

Mon, 01 Jan 0001 00:00:00 +0000

In Google Compute Engine (GCE), an Account maps to a credential able to authenticate against a given Google Cloud Platform (GCP) project.

Prerequisites

You need a Google Cloud Platform (GCP) project to run Spinnaker against. The next steps assume you’ve already created a project , and installed gcloud . You can check that gcloud is installed and authenticated by running:

gcloud info

Downloading credentials

Spinnaker needs a service account to authenticate as against GCE, with the role enumerated below enabled. If you don’t already have such a service account with the corresponding JSON key downloaded, you can run the following commands to do so:

High Availability

Mon, 01 Jan 0001 00:00:00 +0000

HALYARD IS DEPRECATED

Important

The majority of the relevant information has been moved to high-availability documentation

This page describes how you can configure a Halyard deployment to increase the availability of specific services beyond simply horizontally scaling the service. Halyard does this by splitting the functionalities of a service into separate logical roles (also known as sharding). The benefits of doing this is specific to the service that is being sharded. These deployment strategies are inspired by Netflix’s large scale experience .

Horizontally Scale Spinnaker Services

Mon, 01 Jan 0001 00:00:00 +0000

This page will explain under which circumstances it can help to run more than one copy of any single service, and what considerations have to be made when doing so.

This article assumes you have access to scale the individual Spinnaker microservices, and the mechanics of this are not covered here.

Keep in mind, if you are deploying Spinnaker to Kubernetes, you’re more likely to see benefits of horizontal scaling if you’ve already allocated resource requests and limits for the services being scaled.

HTTP File

Mon, 01 Jan 0001 00:00:00 +0000

HTTP file artifacts are references to files stored in plaintext reachable via HTTP. They are generally consumed by stages that read configuration from text files, such as a Deploy Manifest stage.

These files can be downloaded using basic auth.

Fields

Field	Explanation
`type`	Always `http/file`.
`reference`	The fully-qualified URL where your file can be read from.
`name`	An optional identifier for referencing this artifact later.
`version`	N/A
`location`	N/A

Example

{
  "type": "http/file",
  "reference": "https://raw.githubusercontent.com/....",
  "name": "My manifest stored in github",
}

HTTP File

Mon, 01 Jan 0001 00:00:00 +0000

These artifacts are generally consumed by stages that read configuration from text files, such as a Deploy Manifest stage.

A file represented by an HTTP file artifact can be downloaded using HTTP Basic authentication.

HTTP file artifact in the UI

The pipeline UI exposes the following fields for the HTTP file artifact:

Field	Explanation
Account	An HTTP artifact account.
URL	The fully-qualified URL from which the file can be read.

In a trigger

When configuring certain triggers, you can use an HTTP file as an expected artifact.

Integrate your CI

Mon, 01 Jan 0001 00:00:00 +0000

Overview

At Netflix, we built CI integrations to enable features like the Builds view in Spinnaker, fetching artifact metadata and more. You can see the full list of CI features here .

Viewing CI details in Spinnaker

We recently added the option to see CI details in Spinnaker, in a new “Builds” tab. It looks like this:

This is a new tab that can be accessed from the main Spinnaker UI. The UI code (in deck) is calling the gate service to fetch information, and gate is just proxying the call to igor.

An Introduction to Spinnaker: Hello Deployment

Mon, 01 Jan 0001 00:00:00 +0000

This guide will run through the workflow of setting up an example application deployment with Spinnaker. It assumes you already have Spinnaker up and running on AWS or GCE. A guide for installation can be found here .

Below is a diagram of the workflow we will set up.

Set up Jenkins

Jenkins is a powerful continuous integration server that allows us to do several important things:

Poll our Github repository for changes so Spinnaker knows when to run a pipeline.
Compile and build our example application into a .deb package so Spinnaker can bake it on an image. Spinnaker expects all applications to be deployed as deb packages.

Installing Jenkins

If you already have a Jenkins server, you can skip this step.

Jenkins

Mon, 01 Jan 0001 00:00:00 +0000

Setting up Jenkins as a Continuous Integration (CI) system within Spinnaker lets you trigger pipelines with Jenkins, add a Jenkins stage to your pipeline, or add a Script stage to your pipeline.

Prerequisites

To connect Jenkins to Spinnaker, you need:

A running Jenkins Master at version 2.x, reachable at a URL ($BASEURL) from where Spinnaker runs.
A username/API key ($USERNAME/$APIKEY) pair able to authenticate against Jenkins using HTTP Basic Auth, if Jenkins is secured. A user’s API key can be found at $BASEURL/user/$USERNAME/configure.

Add your Jenkins master

Add the following to igor-local.yml to enable Jenkins;

Kubernetes Source to Prod

Mon, 01 Jan 0001 00:00:00 +0000

Overview

In this codelab you will configure:

A GitHub repo containing both your code to be deployed, and the Kubernetes manifests that will run your code.
A set of Spinnaker pipelines to deploy changes to your code, manifests, and application configuration from source to production.

0: Prerequisites

Before we begin, we need to do the following:

Configure GitHub

You need some source code and manifests to deploy stored in GitHub. We have a repository you can fork to follow along easily.

Kubernetes CRD Extensions

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker Extension Points for Custom Resource Definitions

At Google, we’ve built extension points for deep CRD integrations within Spinnaker.

This work has allowed us to support the following features within Spinnaker:

Custom models for representing CRDs as spinnakerKinds
Deploying CRDs with custom Spinnaker artifact types
Custom Kubernetes API versions
Custom Spinnaker naming strategies
Per-account, custom Spinnaker UIs that can run alongside the existing Kubernetes UIs

Kubernetes Object

Mon, 01 Jan 0001 00:00:00 +0000

Kubernetes Object artifacts are running, deployed Kubernetes Manifests. This is in contrast to something like a GitHub file that only contains the specification of a deployable Kubernetes Manifest.

Fields

Field	Explanation
`type`	`kubernetes/<kind>`, where `<kind>` is the Kubernetes Kind, such as `Deployment`.
`reference`	The name of the object.
`name`	The name of the object.
`version`	Only set when the resource was deployed with a version. A `ConfigMap` at version `-v120` is an example.
`location`	The object’s namespace.
`artifactAccount`	The Spinnaker account (Kubernetes context) this was deployed to.

Example

{
  "type": "kubernetes/deployment",
  "reference": "frontend",
  "name": "frontend",
  "namespace": "staging",
  "artifactAccount": "gke-us-central1-xnat"
}

Kubernetes Object

Mon, 01 Jan 0001 00:00:00 +0000

Kubernetes object artifact in the UI

The pipeline UI exposes the following fields for the Kubernetes object artifact:

Field	Explanation
Account	An HTTP artifact account.
URL	The fully-qualified URL from which the file can be read.

Kubernetes object artifact in a pipeline definition

The following are the fields that make up a Kubernetes object artifact:

Field	Explanation
`type`	`kubernetes/<kind>`, where `<kind>` is the Kubernetes Kind (such as `Deployment`).
`reference`	The name of the object.
`name`	The name of the object.
`version`	The version of the object. Only set if the resource was deployed with a version (for example, a `ConfigMap` deployed at version `-v120`).
`location`	The namespace of the object.
`artifactAccount`	The Spinnaker account (Kubernetes context) to which the object was deployed.

The following is an example JSON representation of a Kubernetes object artifact, as it would appear in a pipeline definition:

Kubernetes Provider Overview

Mon, 01 Jan 0001 00:00:00 +0000

If you’re unfamiliar with Kubernetes terminology, see the Kubernetes documentation .

This article describes how the Kubernetes provider works and how it differs from other providers in Spinnaker. If you’re unfamiliar with Kubernetes terminology, see the Kubernetes documentation .

The manifest-based approach

The Kubernetes provider combines the strengths of Kubernetes’s declarative infrastructure management with Spinnaker’s workflow engine for imperative steps when you need them. You can fully specify all your infrastructure in the native Kubernetes manifest format but still express, for example, a multi-region canary-driven rollout.

LDAP

Mon, 01 Jan 0001 00:00:00 +0000

Lightweight Directory Access Protocol (LDAP) is a standard way many organizations maintain user credentials and group memberships. Spinnaker uses the standard “bind” approach for user authentication. This is a fancy way of saying that Gate uses your username and password to login to the LDAP server, and if the connection is successful, you’re considered authenticated. Note that there is a fair bit of crossover between the authorization and authentication settings.

Life of a Bake

Mon, 01 Jan 0001 00:00:00 +0000

sequenceDiagram Title: Life of a Bake participant Igor participant Jenkins participant ArtifactRepo participant Echo participant Front50 participant Orca participant Rosco participant Packer participant Redis participant Cloud Echo->>Front50: Build cache of pipeline triggers Jenkins->>ArtifactRepo: Publish newly-produced deployable asset (e.g. .deb/.rpm/.jar) Note right of Jenkins: Archive artifacts Igor->>Jenkins: Poll Jenkins for completed builds Igor->>Echo: Publish completed build info to eventing bus Echo->>+Orca: Initiate pipeline execution based on matched trigger Orca->>Redis: Persist new execution Note right of Orca: Orca uses the artifact details from the trigger to decorate the package name with version information Orca->>-Rosco: Request bake, passing package with exact version to install Rosco->>Redis: Persist new bake Rosco->>Packer: Initiate bake job, passing repo address (from config) and package/version Packer->>ArtifactRepo: Pull deployable asset from repo Packer->>Cloud: Publish machine image Loop In background thread Rosco->>Packer: Poll until job completion Rosco->>Redis: Mark bake completed end Loop In worker thread Orca->>Rosco: Poll until task completion Rosco->>Redis: Query bake status Orca->>Redis: Update execution state end

Life of a Deployment

Mon, 01 Jan 0001 00:00:00 +0000

sequenceDiagram Title: Life of a deployment participant Deck participant Gate participant Orca participant Clouddriver participant Redis participant Cloud Deck->>+Gate: Initiate Deploy orchestration Gate->>+Orca: Initiate Deploy orchestration Orca->>Redis: Persist new execution Orca-->>-Gate: Reply with orchestration id Gate-->>-Deck: Reply with orchestration id Note right of Orca: In worker thread Orca->>+Clouddriver: Initiate Deploy operation Clouddriver->>Redis: Persist new task Clouddriver-->>-Orca: Reply with task id Clouddriver-xCloud: Mutating calls activate Clouddriver Clouddriver->>Redis: Mark task completed deactivate Clouddriver Loop In worker thread Orca->>Clouddriver: Poll until task completion Clouddriver->>Redis: Query task status Orca->>Redis: Update execution state end Loop In worker thread Orca->>Clouddriver: Poll until instances are up Clouddriver->>Redis: Query server group/instance state from cache Orca->>Redis: Mark execution completed end Loop In background thread Deck->>Gate: Poll until orchestration completion Gate->>Orca: Query orchestration status Orca->>Redis: Query execution status end

Make a Change Using a Local Clone

Mon, 01 Jan 0001 00:00:00 +0000

To make significant changes to a Spinnaker service or other repository, you can fork the repository and work from a local clone. The workflow below walks through a change to the spinnaker/spinnaker.io repository as an example, but a fork-and-pull-request workflow should be used for all Spinnaker contributions. Make sure you have git installed on your computer and have configured your GitHub account. See the GitHub Help for details.

Fork the repository

Navigate to the spinnaker/spinnaker.io repository with a web browser.
Click Fork.

Create a local repository and set the upstream repository

In a terminal window, clone your fork:

Make a Change Using the GitHub Web UI

Mon, 01 Jan 0001 00:00:00 +0000

Open a pull request (PR) on GitHub

Click the Suggest an Edit link on the documentation page you want to update. This takes you to the page’s source file in GitHub.
Click the Edit this file… pencil icon to edit the file.
Make your changes in the GitHub markdown editor.
Fill in the Propose file change form.
1. Explain what your file change is about in a short summary.

Manage Traffic Using Kubernetes Manifests

Mon, 01 Jan 0001 00:00:00 +0000

This guide shows the basics of how to manage traffic during deployments using the Kubernetes provider . This includes automatically attaching a Service to a workload during deployment, and defining pipelines to perform blue/green deployments.

Attach a Service to a Workload

Kubernetes manages the relationship between Pods and Services using Labels and Selectors . Spinnaker acknowledges this relationship with the blue load balancer icon on a workload as shown here:

You can also tell Spinnaker which Service objects a workload should be associated with for its lifetime using the traffic.spinnaker.io/load-balancers annotation. To try this out, do the following:

Managing Deprecations

Mon, 01 Jan 0001 00:00:00 +0000

Deprecating old functionality is key to making Spinnaker easier to maintain, but it needs to be done in a way that is as non-disruptive as possible.

Maven Artifact

Mon, 01 Jan 0001 00:00:00 +0000

These artifacts are generally consumed by stages that deploy application artifacts, such as a Deploy stage.

The files stored in a Maven repository are typically called “artifacts”, so on this page, “Maven artifact” may refer to a Spinnaker artifact of type maven/file or to a file (e.g. a JAR file) stored in a Maven repository.

Maven artifact in the UI

The pipeline UI exposes the following fields for the Maven artifact:

Monitoring

Mon, 01 Jan 0001 00:00:00 +0000

If you’re looking on instructions for how to install or setup monitoring, checkout the Enable Monitoring section in the Spinnaker Setup Guide .

Metrics overview

A Spinnaker metric is a named collection of measurements used to track a type of activity over time. There are two basic types of metrics: counters and gauges. A counter measures how many times the activity occured over the lifetime of the process (e.g. how many actions have ever occurred) whereas a gauge measures an instantaneous value (e.g. how many actions are active now).

Oracle Cloud Infrastructure Source to Prod

Mon, 01 Jan 0001 00:00:00 +0000

In this codelab, you will create a cohesive workflow which takes source code and builds, tests, and promotes it to production.

Building the binary from the source code is done outside of Spinnaker, typically in a CI system such as Jenkins, Travis, etc. Spinnaker is integrated with three CI systems. Workflows can be triggered by jobs in these CI systems. The easiest binary form for Spinnaker to produce machine image is debian or rpm packages.

Oracle

Mon, 01 Jan 0001 00:00:00 +0000

In Oracle Cloud , a Spinnaker Account maps to an Oracle Cloud Infrastructure user .

Prerequisites

You will need the following to enable Oracle Cloud provider in Spinnaker:

A user in IAM for the person or system who will be using Spinnaker, and put that user in at least one IAM group with any desired permissions. See Adding Users .
The user’s home region. See Managing Regions . (e.g. --region us-ashburn-1)
RSA key pair in PEM format (minimum 2048 bits). See How to Generate an API Signing Key . (e.g. --ssh-private-key-file-path /home/ubuntu/.oci/myPrivateKey.pem)
Fingerprint of the public key. See How to Get the Fingerprint of the Key . (e.g. --fingerprint 11:22:33:..:aa)
Tenancy’s OCID and user’s OCID. See Where to Get the Tenancy and User OCIDs . (e.g. --tenancyId ocid1.tenancy.oc1..aa... --user-id ocid1.user.oc1..aa...)
Compartment OCID: On Oracle Cloud Console, open the navigation menu. Under Governance and Administration, go to Identity and click Compartments. See Managing Compartments . (e.g. --compartment-id ocid1.compartment.oc1..aa...)
Upload the public key from the key pair in the Console. See How to Upload the Public Key .

Add an Oracle Cloud account

Enable the Oracle Cloud provider and add the account

oracle:
  enabled: true
  accounts:
  - name: my-oci-acct
    compartment-id: ocid1.compartment.oc1..aaaaaaaatjuwhxwkspkxhumqke4o73b2b
    fingerprint: 8f:05:f4:94:f3:5f:e3:30:ec:35 
    region: us-phoenix-1
    ssh-private-key-file-path: /mnt/secrets/oci_api_key.pem
    tenancyId: ocid1.tenancy.oc1..aaaaaaaa225wmphohi3iiyxxxjruo
    userId: ocid1.user.oc1..aaaaaaaagosdr3zsh67tvgpnmw42ywqc

Next steps

Optionally, you can set up another cloud provider or continue the installation instructions

Oracle Cloud

Mon, 01 Jan 0001 00:00:00 +0000

For more information about Oracle Cloud or any of the terms used below, please consult Oracle Cloud Infrastructure Documentation .

Resource mapping

Account

The Oracle Cloud provider in Spinnaker maps a Spinnaker Account to an Oracle Cloud Infrastructure user in Oracle Cloud Infrastructure (OCI). Spinnaker authenticates itself with Oracle Cloud using OCI user credentials - see the setup guide .

Load Balancer

A Spinnaker load balancer maps to an OCI Load Balancer .

The OCI Load Balancing service offers a load balancer with your choice of a public or private IP address, and provisioned bandwidth. The essential components for load balancing include:

Oracle Cloud

Mon, 01 Jan 0001 00:00:00 +0000

Configuring Oracle Cloud OAuth 2.0

Consult the Oracle Cloud Documentation to set up OAuth 2.0 and obtain a client ID and client secret.

Note: While registering the application in Oracle Cloud OAuth 2.0, application redirect URI that should be used is https://localhost:8084/login/oauth2/code/oracle (For Spinnaker below v2025.2.0, it should be https://localhost:8084/login)

Configure Gate

Add the following to gate-local.yml

spring:
  security:
    oauth2:
      client:
        registration:
          userInfoMapping:
            email: ''
            firstName: given_name
            lastName: family_name
            username: preferred_username
          oracle:
            client-secret: <client-secret>
            scope: openid,urn:opc:idm:__myscopes__
            client-id: <client-id>
            redirect-uri: https://<your-domain>/login/oauth2/code/<providerid-aka-google>
        provider:
          oracle:
            user-info-uri: https://idcs-${idcsTenantId}.identity.oraclecloud.com/oauth2/v1/userinfo
            authorization-uri: https://idcs-${idcsTenantId}.identity.oraclecloud.com/oauth2/v1/authorize
            token-uri: https://idcs-${idcsTenantId}.identity.oraclecloud.com/oauth2/v1/token

For versions prior to 2025.2.0

Add the following to gate-local.yml

Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) Setup

Mon, 01 Jan 0001 00:00:00 +0000

This page describes how to set up a Kubernetes cluster on OKE to be used with Spinnaker’s Kubernetes provider.

Create a cluster

If you don’t already have a cluster for this purpose, you can create a Kubernetes cluster on OKE by following this tutorial .

Download kubectl configuration file

Follow the instructions to download kubectl configuration file.

Store the config file in a secret that spinnaker can reference

kubectl create secret generic my-secret --from-file=kubeconfig-my-account=./kubeconfig

For additional entries you may need to determine an alternative strategy or use an external secrets manager instead of directly mounting secrets onto pods.

Oracle Object

Mon, 01 Jan 0001 00:00:00 +0000

Oracle Object Storage is an object store, and Oracle Object Storage object artifacts are references to objects stored in Oracle Object Storage buckets. These artifacts are generally consumed by stages that read configuration from text files, for example a Deploy Manifest stage.

Fields

Field	Explanation
`type`	Always `oracle/object`.
`reference`	The `oci://`-prefixed reference to your file. Following the bucket name is the path to your file.

Example

{
  "type": "oracle/object",
  "reference": "oci://bucket/file.json"
}

Oracle Object

Mon, 01 Jan 0001 00:00:00 +0000

These artifacts are generally consumed by stages that read configuration from text files, such as a Deploy Manifest stage.

Oracle object artifact in a pipeline definition

The following are the fields that make up an Oracle object artifact:

Field	Explanation
`type`	Always `oracle/object`.
`reference`	The full path to the artifact file, beginning with`oci://`.

The following is an example JSON representation of an Oracle object artifact, as it would appear in a pipeline definition:

Orca Internals Overview

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker is known and often loved for enabling accessible, highly configurable and composable workflows through its pipelines and tasks. This is largely thanks to the code that makes up Orca.

From Orca’s README :

Orca is the orchestration engine for Spinnaker. It is responsible for taking a pipeline or task definition and managing the stages and tasks, coordinating the other Spinnaker services.

Orca is a stateless, horizontally scalable service. Spinnaker’s execution state is persisted to a backend store and work is distributed evenly through a work queue. So long as your backend persistence layer has capacity, you can freely add or remove Orca servers to match workload demands.

Parameterize Kubernetes Manifests

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker can inject context from the currently executing pipeline into your manifests as they are deployed, whether they are deployed statically or dynamically .

This can be applied to a wide range of use-cases, but we will focus on using a pipeline parameter to specify the target namespace.

Configure your pipeline parameters

First, register a pipeline parameter in the “configuration” tab of the pipeline editor (only the Name is required):

See more details on how to provide parameters to pipelines programmatically in the webhooks page.

Patch Kubernetes Manifests

Mon, 01 Jan 0001 00:00:00 +0000

This guide shows the basics of how to update a Kubernetes resource in place using the patch manifest stage for the Kubernetes provider provider.

There are a few steps:

Specify which manifest to patch
Specify the patch content
(Optional) Override artifacts in the patch content

Optionally, you can override some artifacts (as fields) at run time (for example, which Docker image to use.)
(Optional) Override patch specific options

Specify the resource to patch

Start by selecting the Patch (Manifest) stage from the stage selector:

To identify the Kubernetes resource to patch, specify the following required fields:

Field	Value
Account	The Spinnaker account that manages the Kubernetes cluster
Namespace	The Kubernetes namespace that your resource is located in
Kind	The Kubernetes Kind of your resource e.g. deployment, service etc
Name	The name of your Kubernetes resource

Specify your patch content

The patch content is similar to a manifest in the Deploy (Manifest) stage. However, unlike the deploy manifest, this does not have to be the full resource manifest but only the portion you want to patch.

Plugin Compatibility Testing

Mon, 01 Jan 0001 00:00:00 +0000

A plugin can be executed inside of a Spinnaker version that is different than the version it was compiled against. For example, a plugin compiled against Spinnaker 1.20 might be compatible with Spinnaker versions up to 1.23.

This range is important for plugin developers so that they can support users across Spinnaker versions; it’s important for plugin consumers so that they can safely install and upgrade plugins. Fortunately, testing can resolve this compatibility range automatically.

Plugin Project Configuration

Mon, 01 Jan 0001 00:00:00 +0000

The contents of this page refer to alpha features in Spinnaker 1.19.4.

This means we are working on their stability and usability, as well as possibly adding or changing features. Expect rough edges, and file issues as needed.

This guide is a work in progress. Help us improve the content by submitting a pull request!

Project Configuration

Keep the following recommendations and requirements in mind: - We recommend making the project a Gradle project. There is Gradle tooling to support plugin development. - You can add any dependencies you need to make your plugin successful.. TODO-CF this is almost certainly a lie when it comes to things that conflict with the dependencies in the compileOnly scope…

Plugin Project Configuration

Mon, 01 Jan 0001 00:00:00 +0000

Plugins are an evolving feature. The easiest way to set up a new plugin project is to copy one of the spinnaker-plugin-examples projects that most closely resembles what you want to do.

Gradle configuration

Some important aspects of your project’s gradle build:

gradle.properties

Organizing these values into gradle.properties is optional, but these versions are very much mandatory.

spinnakerGradleVersion=8.10.1
pf4jVersion=3.2.0
korkVersion=7.99.1
orcaVersion=2.19.0-20210209140018
kotlinVersion=1.3.50

Note that managing the version of your plugin here (version=1.2.3) requires modifying this file for each release. There are fancier ways (the example project uses a git tag strategy and additional gradle plugins) but those are outside the scope of this documentation.

Pull Requests and Changes

Mon, 01 Jan 0001 00:00:00 +0000

Change Process

Once you’ve implemented a bug fix or feature, it’s time to submit a pull request to Spinnaker. We recommend small, well-tested pull requests as a starting point for new technical contributors. For information on the correct fork-and-PR GitHub workflows to follow when contributing, reference the local clone guide.

To work on bigger technical changes, follow the feature proposal or RFC processes.

Pull Request Tips

Check that your title describes your changes and adheres to our message conventions .
Add inline code comments to changes that might not be obvious.
Squash your commits into logically reviewable chunks when you first submit your PR. Address feedback in follow-up (unsquashed) commits. It’s much easier to review incremental changes to feedback when the commits are kept separate.
All pull requests should get reviewed by at least one other member of the Spinnaker organization before merging. (While some members of the organization have access to merge without a review, this should only be done in an emergency or when merging a large series of dependency bumps across repositories.)
Squash your commits when merging to the branch.

Commit and PR message conventions

Please follow conventions below in your git commit messages. Since GitHub auto-fills Pull Request titles from the first commit message of the PR, following these conventions should help to title your PRs according to our community standards.

Reviewing Pull Requests

Mon, 01 Jan 0001 00:00:00 +0000

Review a Pull request

Anyone can review a documentation pull request (PR). Visit the Pull requests section in the Spinnaker website repository to see a list of all currently open pull requests.

Reviewing documentation pull requests is a great way to get started contributing to the Spinnaker community. It helps you to learn the code base and builds rapport with other contributors.

Before you begin

Before reviewing documentation, do the following:

Roadmap

Mon, 01 Jan 0001 00:00:00 +0000

Project Roadmap

Enhancements in upcoming releases without a schedule

These improvements could happen at ANY time in any of the releases. We’d welcome input on additional features that people would like to see from the project!

Add a native MCP endpoint. There’s a few publicly available MCP servers, but having one natively supported would be ideal
UI to add/remove accounts. Make dynamic accounts a “default”. This support was added back in 1.28 and enhanced at various times, but we’d like to fully enable AND default this support to on
Replace the “kubectl” based execution of kubernetes operations to native kubernetes SDK operations.
AWS Lambda to async for invocations. Currently lambda operations (primarily invocations) are “SYNCHRONOUS” calls. The plan is to change these to an ASYNC which captures the execution from AWS & polls for completion instead of keeping the network connection open. This is critical for long running operations.
CI: Add a couple of CI providers to enable the UI to show build information. This is already in the codebase and documented but actually adding a few providers and possibly fixing issues around showing CI integration would be of use.
Bring in changes from forks. There’s a few forks that have nice features we could bring in at anytime. Azure fixes and some UI tweaks.
Move igor to use SQL instead of redis
Move rosco to use SQL instead of redis

2026.3.0

Primary goal is the removal and upgrade of some core libraries. We’ll be marking several things as deprecated as we plan to remove them.

Add API token support to the spin CLI with the new feature
Make several older configs default to on going forward (API token, some other default settings)
Pub/Sub -> Introduce a “pub/sub” based cache scheduler. The primary driver here would be to add a native spring approach for queueable operations vs custom queue or task operations. Add libraries to support this in kork-pub-sub. Cleanup the various pubsub implementations (echo & kork) to be centralized via kork library handling.
GCP - additional support for some google features like regional external load balancers.
Full V2 SDK for AWS API operations. Thanks to some contributions, we should be on or nearly fully on a v2 of the AWS SDKs.
s3/gcs storage in front50 as deprecated. We plan to remove all storage support for front50 for anything other than SQL. This should simplify the codebase quite a bit.
Remove halyard. We’d marked it deprecated in favor of a kustomize example but plan to fully remove and stop patching it going forward.
Remove edda (part of AWS v2 migration). This is already NOT supported on new V2 efforts but will remove it from the codebase entirely.
Deprecate titus from the project
Deprecate redis as a backend for orca storage (NOT scheduler, just storage of executions)
Continue removal of Angular for React components
Change information on observability from Armory’s observability agent to using OTEL
Upgrade the docs site to latest releases of docsy & hugo (enables a number of features)
Remove “OnDemand” system. There’s only one scheduler that works with it and it is not a viable scheduler. This will simplify cache operations.

Stretch goals

We’d like to do some additional “cleanup” tasks. Some of these are more difficult than others but would welcome PRs to assist!

Rollout Strategies

Mon, 01 Jan 0001 00:00:00 +0000

This guide describes how to take advantage of the Kubernetes provider’s first-class support for common rollout strategies, including dark, highlander, and blue/green rollouts.

The implementation of these rollout strategies currently leverages Spinnaker’s existing traffic management strategy and is valid for ReplicaSets only. See traffic management for more information.

Rollout Strategy Options

As of version 1.14, you will notice a Rollout Strategy Options section in the Deploy (Manifest) stage. When enabled, these configuration options allow you to associate a workload with one or more services, decide whether the workload should receive traffic, and determine how Spinnaker should handle any previous versions of the workload in the same cluster and namespace.

Run Job (Manifest) Stage

Mon, 01 Jan 0001 00:00:00 +0000

The Run Job (Manifest) stage can be used to execute a Kubernetes Job as part of your pipeline. This stage will deploy a Job manifest and wait until it completes, allowing you to gate your pipeline’s continuation on the job’s success or failure.

For example use cases, check out this post on the Spinnaker blog!

Viewing execution logs

As with any job runner, logs are the primary form of feedback and it’s important that viewing them is a first-class experience within Spinnaker. Since users of Spinnaker are all at various stages of Kubernetes adoption we’ve provided 2 ways to view logs within Spinnaker.

S3 Object

Mon, 01 Jan 0001 00:00:00 +0000

S3 is an object store, and S3 object artifacts are references to objects stored in S3 buckets. These artifacts are generally consumed by stages that read configuration from text files, such as a Deploy Manifest or AWS Deploy stage.

Fields

Field	Explanation
`type`	Always `s3/object`.
`name`	Name/Path of the object.
`reference`	Name/Path of the object.
`location`	The region where your bucket was created

Example

{
  "type": "s3/object",
  "name": "s3://bucket/file.json",
  "reference": "s3://bucket/file.json",
  "location": "us-east-1"
}

S3 Object

Mon, 01 Jan 0001 00:00:00 +0000

These artifacts are generally consumed by stages that read configuration from text files, such as a Deploy Manifest or AWS Deploy stage.

S3 object artifact in the UI

The pipeline UI exposes the following fields for the S3 object artifact:

Field	Explanation
Account	An S3 artifact account.
Object path	The full path to the artifact file, beginning with `s3://`.

In a trigger

When configuring a trigger, you can use an S3 object as an expected artifact.

Safe Deployments

Mon, 01 Jan 0001 00:00:00 +0000

Overview

In this codelab, you will improve a deployment process by adding safeguards to your deployments.

This codelab is a continuation of the Kubernetes: code to prod codelab. It assumes you have an application set up and ready to deploy.

Setup

Please follow the steps in the Kubernetes Source to Prod guide to create a deployed Spinnaker cluster.

Making manual operations safer

Using the Rollback action

The rollback action automates the process of restoring to the previous good known server group. This feature enhances a traditionally manual operation by ensuring that the restored cluster is taking traffic before disabling the current server group.

SAML 2.0

Mon, 01 Jan 0001 00:00:00 +0000

Security Assertion Markup Language (SAML) is an XML based way to implement single sign-on (SSO).

A cryptographically signed XML document (known as a “SAML Assertion”) is sent to the API gateway server (Gate) with your identifying information, such as username and group membership.

Gate verifies the XML document’s signature using a metadata file, and if successful, it associates the identifying information with the user and allows the user to proceed as authenticated.

Search Results

Mon, 01 Jan 0001 00:00:00 +0000

Secrets in GCS

Mon, 01 Jan 0001 00:00:00 +0000

This example uses a bucket (mybucket) to store GitHub credentials and a kubeconfig file.

Authorization

Since you’re storing sensitive information you protect the bucket by restricting access to it. Encryption at rest is already provided automatically without additional setup.

Remember to run Spinnaker services with a service account that allows them to read that content.

Storing secrets

Storing credentials

Store your GitHub credentials in mybucket/spinnaker-secrets.yml:

github:
  password: <PASSWORD>
  token: <TOKEN>

Note: You could choose to store the password under different keys than github.password and github.token. You’d just need to change how to reference the secret .

Secrets in Google Secret Manager

Mon, 01 Jan 0001 00:00:00 +0000

This example uses secrets - mysecret1, mysecret2 - to store GitHub credentials and secret - mykubeconfig - to store kubeconfig file.

Authorization

Since you’re storing sensitive information you protect the secret by restricting access to it through IAM roles . Encryption at rest is already provided by default.

Remember to run Spinnaker services with a service account that allows them to read that content.

Storing secrets

Storing credentials

Store your GitHub token in a secret named mysecret either as a complete secret or as a value of one of the json keys:

Secrets in S3

Mon, 01 Jan 0001 00:00:00 +0000

This document describes how to set up Spinnaker secrets in an encrypted S3 bucket. This example uses a bucket ( mybucket) in the us-west-2 region to store GitHub credentials and a kubeconfig file. You can reference the bucket by its URL mybucket.us-west-2.amazonaws.com.

Authorization

Since you’re storing sensitive information, you protect the bucket by restricting access and enabling encryption .

Remember to run Spinnaker services with IAM roles that allow them to read that content.

Set up Clouddriver to use SQL

Mon, 01 Jan 0001 00:00:00 +0000

These are:

Caching the state of all supported cloud resources and graphing their relationships
The cloud operations task repository
Distributed locking for the caching agent scheduler

You can also use Redis for one of the above, and SQL for another. A DualTaskRepository class is provided to enable online migrations between Redis and SQL in either direction without impact to running pipelines.

This guide covers database and Clouddriver configuration details, as well as tips on how Clouddriver is operated at Netflix.

Set up Front50 to use SQL

Mon, 01 Jan 0001 00:00:00 +0000

You can configure Front50 to use a MySQL compatible database in place of any cloud provider-specific storage service (S3, GCS, etc.).

A migration can be performed without downtime by taking advantage of the dual-read/write capabilities in the provided CompositeStorageService.

Why SQL

Netflix has been plagued by eventual consistency-related issues around our usage of versioned S3 buckets and Front50’s expectations around read-after-write consistency.

Attempts to work around S3’s consistency model have resulted in an operationally complicated production deployment.

Set up Orca to use SQL

Mon, 01 Jan 0001 00:00:00 +0000

Orca’s execution state is stored in Redis by default, but can be configured for SQL. In this topology, Redis is still required for the work queue. Using SQL for execution state will make your Spinnaker installation more durable.

This guide will go over MySQL setup, how to configure Orca, as well as how to perform a zero-downtime migration from Redis to SQL.

If you already have an Orca deployment, you should also refer to the Redis to SQL Migration Guide .

Spinnaker Special Interest Groups

Mon, 01 Jan 0001 00:00:00 +0000

Information about Spinnaker SIGs has been moved to the governance repository

SSL

Mon, 01 Jan 0001 00:00:00 +0000

This section covers communication with Spinnaker from parties external to your Spinnaker instance. That is, any requests between…

your browser and the Spinnaker UI (Deck)
Deck and Gate (the API gateway)
any other client and Gate

Network configurations

Warning: Many operators like to get authentication working before adding HTTPS, but experience bears out that the transition is not smooth. We recommend you implement at least a temporary SSL solution first.

Pipeline Stage Plugin Walkthrough

Mon, 01 Jan 0001 00:00:00 +0000

The contents of this page refer to alpha features in Spinnaker 1.19.4.

This means we are working on their stability and usability, as well as possibly adding or changing features. Expect rough edges, and file issues as needed.

This guide is a work in progress. Help us improve the content by submitting a pull request!

Requirements

You have read the Plugin Creators Guide Overview .
Gradle and Yarn for building the plugin locally
IntelliJ IDEA, Orca branch release-1.19.x and Deck branch for local testing
Spinnaker current release for deploying the pf4jStagePlugin 1.0.16

pf4jStagePlugin plugin

The pf4jStagePlugin creates a custom pipeline stage that waits a number of seconds before signaling success. The plugin consists of a random-wait-orca Kotlin server component and a random-wait-deck React UI component.

Support Policy

Mon, 01 Jan 0001 00:00:00 +0000

Q&A

If you have a question that isn’t answered by our documents and FAQ pages, please reach out for help on Slack .

The Spinnaker team hangs out on Slack in both the #general channel for general user-related discussions and the #dev channel for developer-related discussions. Additionally, Special Interest Groups (SIGs) have dedicated Slack channels, like #sig-security for the Security SIG.

Slack requires registration, but the Spinnaker team is open invitation to anyone to register here . Feel free to come and ask any and all questions.

Swagger UI

Mon, 01 Jan 0001 00:00:00 +0000

If you installed Spinnaker, and the API gateway Gate is running and accessible (e.g., at localhost:8084 ), navigate to <gate_endpoint>/swagger-ui/index.html in your browser to view the auto-generated Swagger UI.

Some of the other Spinnaker services, such as Clouddriver, Front50, and Rosco, have their own Swagger UIs. These are each accessible at <service_endpoint>/swagger-ui/index.html.

Test a Pipeline Stage Plugin

Mon, 01 Jan 0001 00:00:00 +0000

Overview

This document is deprecated and out of date. Halyard is no longer supported but the document is being left as a useful reference

This guide explains how to set up a local Spinnaker environment on your Mac or Windows environment so you can test the pf4jStagePlugin, which has both Orca and Deck components. Spinnaker services running locally communicate with the other Spinnaker services running in a local VM. Although this guide is specific to the pf4jStagePlugin, you can adapt its contents to test your own plugin.

Travis CI

Mon, 01 Jan 0001 00:00:00 +0000

You can configure Spinnaker to use Travis CI as your Continuous Integration system, trigger pipelines with Travis, or add a Travis stage to a pipeline.

Prerequisites

You need a Travis user with an API access token so that you get only the repos you should see.
That user needs adequate access in GitHub to trigger builds.

Add your Travis CI master

Enable Travis CI in igor-local.yml

travis:
  enabled: true
  masters:
  - name: someName
    baseUrl: https://travis-ci.com
    ## Address IS Required but MAY not be actually used anymore
    address: https://api.travis-ci.com
    githubToken: patUse
    numberOfJobs: number to poll for each cycle

It is recommended to use encrypted secrets for password information in the above

try.spinnaker.io

Mon, 01 Jan 0001 00:00:00 +0000

Goal: One of the best ways to learn Spinnaker is to use Spinnaker. This project provides a hosted playground version of Spinnaker aimed for new users to test out its UI and core features.

Status: Active

Source Code: https://github.com/spinnaker/try.spinnaker.io

Team

Student: Daniel Ko
Mentor(s): Fernando Freire, Dan Johnston, Cameron Motevasselani

Details

Background

Spinnaker is a mature open source continuous delivery software platform used and contributed by Fortune 500 companies such as Netflix and Google. A common pain point for users who wish to test out Spinnaker is the overwhelming complexity of the setup process; users must have a Kubernetes cluster to deploy client applications, figure out what environment to deploy Spinnaker, and deal with a laundry list of configuration settings such as storage devices and authentication.

Use Kustomize for Manifests

Mon, 01 Jan 0001 00:00:00 +0000

Kustomize is a tool that lets you create customized Kubernetes deployments without modifying underlying YAML configuration files. Since the files remain unchanged, others are able to reuse the same files to build their own customizations. Your customizations are stored in a file called kustomization.yaml. If configuration changes are needed, the underlying YAML files and kustomization.yaml can be updated independently of each other.

To learn more about Kustomize and how to define a kustomization.yaml file, see the following links:

User Data Files and Metadata

Mon, 01 Jan 0001 00:00:00 +0000

Spinnaker refers to data injected into instances started by Spinnaker as user data. The implementation and naming of this varies from provider to provider, but the resulting functionality is similar. In AWS, it is known as User Data . In GCP, it is known as Instance Metadata . The template file used to define the user data is called the user data file which is located on the Clouddriver server. Tokens are replaced in the user data file to provide some specifics about the deployment. Every instance started has environment variables are set according to the template and the deployment. This feature is currently supported with the AWS and GCP providers.

Versions

Mon, 01 Jan 0001 00:00:00 +0000

The Spinnaker releases listed below are top-level versions tying together each Spinnaker subcomponents’ versions.

These have been validated together in an end-to-end integration test suite curated by the Spinnaker community, and represent a more maintainable, easy to upgrade Spinnaker.

While it’s still possible to install each Spinnaker subcomponent’s versions independently, there is no guarantee that they will work together.

If you want to see what each top-level version is comprised of, run

Videos

Mon, 01 Jan 0001 00:00:00 +0000

Subscribe to the Spinnaker YouTube channel

General

Welcome to Spinnaker: Feature Overview (2m 46s)

Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.

Disabling a Spinnaker pipeline (0m 58s)

In Spinnaker, you can disable a pipeline, which means it will not automatically trigger on external events; moreover, a disabled pipeline cannot be executed manually.

Manually triggering a Spinnaker pipeline (0m 46s)

This video demonstrates how to manually kickoff a pipeline (even if it’s been configured to automatically trigger on an event, such as a crontab).

Writing a New Stage

Mon, 01 Jan 0001 00:00:00 +0000

Overview

To create a new stage, you need to make backend changes to orca to implement the logic of the stage, and the front-end changes to Deck to implement the UI. Depending on what the stage does, you may need to implement new cloud provider-specific logic into Clouddriver as well.

This doc currently only covers the backend changes made to orca.

Backend (orca)

For the backend, you need to define:

A stage class
One or more task classes associated with the stage

Stage class

A stage class must implement the com.netflix.spinnaker.orca.pipeline.StageDefinitionBuilder interface.

X.509 Client Certificates

Mon, 01 Jan 0001 00:00:00 +0000

X.509 client certificates utilize public-key infrastructure (PKI) in order to authenticate clients. X.509 can be used simultaneously with one of the other authentication methods or by itself. Users commonly generate a certificate for their non-UI or script based clients, as this is generally easier than dynamically obtaining an OAuth Bearer token or SAML assertion.

Certificates

If you followed the SSL guide, you may already have generated a certificate authority (CA). Using this CA, we can generate a client certificate using openssl.