Releases on Spinnaker

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.

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!

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.

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