spinnaker-release

Spinnaker Release 1.18.0

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.

Support for deploying and managing Alibaba Cloud load balancers

Support for executing CloudFormation ChangeSet

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.

spinnaker-release

Spinnaker Release 1.19.0

Note: This release requires Halyard version 1.32.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.

Scheduled Removal of Kubernetes V1 Provider

The Kubernetes V1 provider will be removed in Spinnaker 1.21. Please see the RFC for more details.

Breaking change: Kubernetes accounts with an unspecified providerVersion will now default to V2. Please update your halconfig to specify providerVersion: v1 for any Kubernetes accounts you are currently using with the V1 provider.

spinnaker-release

Spinnaker Release 1.18.6

Note: This release requires Halyard version 1.29.0 or later.

Clouddriver 6.6.1

Fixes

• cloudFoundry: fix cloudFoundry job provider (#4379) (7118dfa5)
• ecs: Improve debug messaging for task health (#4431) (395ed92f)
• ecs: Prevent NPE when a task def ARN is no longer in the cache (#4338) (cf7f8d9f)
• ecs: provide port mappings if legacy target group setting is set (#4340) (e2c48d45)
• ecs: only add service role to create request if there is one lb (#4349) (af278e44)

spinnaker-release

Spinnaker Release 1.19.1

Note: This release requires Halyard version 1.32.0 or later.

Clouddriver 6.7.0

Fixes

• ecs: Improve debug messaging for task health (#4431) (0c2e70cc)
• ecs: Correctly scope TargetHealthCachingAgent describe calls (#4429) (bf707f58)
• ecs: Remove extra evictions from TaskHealthCachingAgent (#4417) (390f30e8)
• sql: use jooq constructs instead of string constructs (#4412) (4e3f97ff)

spinnaker-release

Spinnaker Release 1.19.0

Note: This release requires Halyard version 1.32.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.

Scheduled Removal of Kubernetes V1 Provider

The Kubernetes V1 provider will be removed in Spinnaker 1.21. Please see the RFC for more details.

Breaking change: Kubernetes accounts with an unspecified providerVersion will now default to V2. Please update your halconfig to specify providerVersion: v1 for any Kubernetes accounts you are currently using with the V1 provider.

spinnaker-release

Spinnaker Release 1.18.5

Note: This release requires Halyard version 1.29.0 or later.

Clouddriver 6.5.4

Fixes

• cloudFoundry: fix cloudFoundry job provider (#4379) (7118dfa5)
• ecs: Prevent NPE when a task def ARN is no longer in the cache (#4338) (cf7f8d9f)
• ecs: provide port mappings if legacy target group setting is set (#4340) (e2c48d45)
• kubernetes: return provider field with kubernetes /search results (#4249) (e706eb34)
• repository: Enforce serialization order for JedisTask (#4394) ([deab4921](https://github.com/spinnaker/clouddriver/commit/deab4921f2bb43b136de39df22070e360ce63

spinnaker-release

Spinnaker Release 1.17.7

Clouddriver 6.5.4

Fixes

• aws: support for cross-application CLBs with the sql backend (#4141) (e1920262)
• cats/sql: fix table names with long type names (#4166) (024b9220)
• cats/sql: fix table names with long type names (024b9220)
• cats/sql: Hash once (024b9220)
• cfn: do not add roleARN if empty or null (#4206) (22f81504)
• cloudFoundry: fix cloudFoundry job provider (#4379) ([ecbed26f](https://github.com/spinnaker/clouddriver/commit/ecbed26faf2778740dba2c46b4ac4e481

spinnaker-release

Spinnaker 1.16.7

Clouddriver 6.3.5

Fixes

• cloudFoundry: fix cloudFoundry job provider (#4379) (4d28d943)

Deck 2.12.5

Other

• buildtool: add an empty .gcloudignore file (#7909) (150ec8bf)
• container builds: exclude large cache directories from GCB upload (#7919) (09050af8)

spinnaker-release

Spinnaker Release 1.18.4

Note: This release requires Halyard version 1.29.0 or later.

Clouddriver 6.5.3

Fixes

• ecs: only add service role to create request if there is one lb (#4349) (af278e44)

Spinnaker Release 1.18.3

Note: This release requires Halyard version 1.29.0 or later.

spinnaker-release

Spinnaker Release 1.18.0

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.

Support for deploying and managing Alibaba Cloud load balancers

Support for executing CloudFormation ChangeSet

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.