Note: This release requires Halyard version 1.29.0 or later.
Clouddriver 6.5.3
- ecs: only add service role to create request if there is one lb (#4349) (af278e44)
Note: This release requires Halyard version 1.29.0 or later.
Note: This release requires Halyard version 1.29.0 or later.
Note: This release requires Halyard version 1.29.0 or later.
Note: This release requires Halyard version 1.29.0 or later.
This release includes fixes, features, and performance improvements across a wide feature set in Spinnaker. Here we share a summary of notable improvements, followed by the comprehensive changelog.
CloudFormation stage allows you to create a change set that allows users to review the changes on the AWS infrastructure before applying them. This new feature enables users to pause the pipeline execution until the user executes the change manually through Deck itself without having to go to AWS console. Users can also configure pre-defined behaviour when the created change set contains a "replacement" in CloudFormation jargon, which can protect users from data-loss and unrecoverable changes in the infrastructure.
The ECS provider now supports routing traffic from multiple load balancers to your ECS service.
View your pod initContainer and container logs side by side from the Spinnaker UI.
Errors emitted from gcloud while deploying to AppEngine will now be surfaced via the pipeline json and the pipeline UI.
The Managed Pipeline Templates V2 UI now displays all versions of a given template. Individual template versions can be viewed, deleted, or used to create a new templated pipeline.
The new Evaluate Variables stage UI allows you to preview the value of your SpEL expressions against past executions.
Added plugin metadata repository to act as source of truth for installed plugins within a spinnaker installation.
The Google Cloud Build stage now provides first-class support for invoking Cloud Build triggers.
There were already retries, but now there is also backoff.
Spinnaker’s community stats are now available for users wishing to opt-in. When enabled, the telemetry module sends data about all completed pipelines to a centralized service. See more details in this blog post.
The Java 11 JRE runs Front50 and Igor when deployed to a Kubernetes cluster using Halyard (or if you consume the official containers in some other way). If this causes problems, or your organization isn't ready to run Java 11 in production, you can specify deploymentEnvironment.imageVariant: JAVA8
(or UBUNTU_JAVA8
) in your Halyard config. Please notify sig-platform@spinnaker.io if you run into issues and decide to downgrade.
All users need to switch to a Java 11 JRE by Spinnaker 1.21, which is scheduled to be released in early July. We encourage everyone to start testing Spinnaker under a Java 11 JRE now in preparation for the cutover. If you have any concerns about the migration timeline, please reach out to sig-platform@spinnaker.io.
Resources from deleted Spinnaker accounts will now be purged from the SQL cache automatically. Enable the cleanup agent by adding sql.unknown-agent-cleanup-agent.enabled: true
to your clouddriver-local.yml
.
The Kubernetes V1 provider will be removed in release 1.21. Please check out the RFC for more details.
list
endpoints as the current implementation is a performance liability (c4411eb6)(#7774) (b05520bc)
(b05520bc)
pipeline.expectedArtifacts.boundArtifact
(df71ed99)