X-SAGA) (6dd6e29b)jobId provided to UpsertTitusScalingPolicy operation (51ec63d5)updateTitusJobProcesses andupsertTitusJobDisruptionBudget are now implemented as sagas (43ea1c8f)upsertScalingPolicy is now implemented as a saga for Titus (a88094d1):clouddriver-configserver to be excluded (dc9e7e4f)createSecurityGroup (7f1f551e)instanceType (4e0e57c0)LaunchFailureNotificationAgent runs against (53ff6c73)AbstractAccountCredentials (4d5c4432)@JsonIgnore so that the attribute is actually ignored (d413d4d1)parseSagaResult can be null (7067abaf)BlockDeviceConfig for new ec2 instance types (e99e0939)BlockDeviceConfig for p4d.24xlarge (dbfc9ece)aws and aws-minimal provider config (ac02c2e5)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. This section provides a summary of notable improvements followed by the comprehensive changelog.
Official Spinnaker Kubernetes containers have moved from
gcr.io/spinnaker-marketplace to
us-docker.pkg.dev/spinnaker-community/docker.
If you use Halyard to deploy your containers, this shouldn't affect you. Halyard will automatically use the new location, since it's written in the BOM files that Halyard uses to get release information.
All releases are available in the new location. Only releases prior to 1.23 are available in the old location, and the old location will be disabled in 2021.
The Bake (manifest) stage now accepts git/repo artifacts when baking a helm chart. See this issue for background.
The Amazon ECS provider now supports using a capacity provider strategy to deploy your ECS service.
If the selected ECS cluster has one or more capacity providers configured, users can provide a list of strategies leveraging those capacity providers to use for their ECS service deployment. In order to add the built-in FARGATE and FARGATE_SPOT capacity providers to an existing cluster, run the following:
aws ecs put-cluster-capacity-providers \
--cluster $MY_CLUSTER \
--capacity-providers FARGATE FARGATE_SPOT \
--region $AWS_REGION
NOTE: If a capacityProviderStrategy is specified, the launchType parameter must be omitted. This means that in case of downgrading Spinnaker from 1.24 to a previous version, server groups which may have used capacity provider strategy will need to be updated to again specify the correct launch type.
The Amazon ECS provider now supports a tag-based Moniker naming strategy for server groups. Users can opt-in to the use of monikers at the ECS provider level or on a per-account basis by specifying the "tags" naming strategey in their hal config:
ecs:
enabled: true
defaultNamingStrategy: "default" <--- 'default' naming used by default (field absent) or if specified
accounts:
- name: "ecs-moniker-acct"
awsAccount: "ec2-aws-acct"
namingStrategy: "tags" <--- 'tags' specified for specific account
NOTES:
SpinnakerManaged role will now need to call ecs:ListAccountSettings in order to validate whether your account is compatible with tags.moniker values for app, stack, and detail to match top-level application, stack, and freeFormDetails values if both are present. Existing pipelines which contain both with different values will need to remove one set or update them to match.Starting in 1.24, the Amazon ECS provider will only cache task definitions associated with Amazon ECS services. Previously, every "active" task definition in the account would be cached, regardless of association with a service. This change does not entail any user-facing changes, but operators may notice a smaller cache footprint and fewer API calls to Amazon ECS.
X-SAGA) (6dd6e29b)jobId provided to UpsertTitusScalingPolicy operation (51ec63d5)updateTitusJobProcesses andupsertTitusJobDisruptionBudget are now implemented as sagas (43ea1c8f)upsertScalingPolicy is now implemented as a saga for Titus (a88094d1):clouddriver-configserver to be excluded (dc9e7e4f)createSecurityGroup (7f1f551e)instanceType (4e0e57c0)LaunchFailureNotificationAgent runs against (53ff6c73)AbstractAccountCredentials (4d5c4432)@JsonIgnore so that the attribute is actually ignored (d413d4d1)parseSagaResult can be null (7067abaf)BlockDeviceConfig for new ec2 instance types (e99e0939)BlockDeviceConfig for p4d.24xlarge (dbfc9ece)aws and aws-minimal provider config (ac02c2e5)app/types typeRoot to all the tsconfig.json files providing PromiseLike and *.svg imports (e622a534)pollingEnabled setting (1699927a)pinned from serialized Capacity objects (370ce376)pinned from serialized Capacity objects (370ce376)