Skip to content

Metadata for v0.2.0 #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
WilboMo merged 1 commit into from
Aug 12, 2021
Merged

Metadata for v0.2.0 #104

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,11 @@
# 0.2.0

* Add support for clusters larger than 50 container instances.
* Add after-action summary and done message to log output.
* Add check to reduce the chance of concurrent runs.

Note: In the Bottlerocket ECS updater v0.1.0 release, support for clusters was limited to 50 container instances. In this release, clusters larger than 50 container instances are now supported. :tada:

# 0.1.0

Initial release of the **Bottlerocket ECS updater** - A service to automatically manage Bottlerocket updates in an Amazon ECS cluster.
Expand Down
3 changes: 0 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -152,9 +152,6 @@ A container instance may be skipped for update when:
The Bottlerocket ECS Updater uses newer [`apiclient update` commands](https://github.com/bottlerocket-os/bottlerocket#update-api) that were added in version [1.0.5](https://github.com/bottlerocket-os/bottlerocket/blob/develop/CHANGELOG.md#v105-2021-01-15).
The SSM commands will fail if your Bottlerocket OS version is less than 1.0.5.
Instances running Bottlerocket versions less than 1.0.5 need to be manually updated.
* _Too many instances are in the cluster._
The Bottlerocket ECS Updater currently supports clusters of up to 50 container instances.
If the updater is configured to target a cluster with more than 50 instances, some instances may not be updated.

### Why do new container instances launch with older Bottlerocket versions?

Expand Down
2 changes: 1 addition & 1 deletion stacks/bottlerocket-ecs-updater.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Parameters:
UpdaterImage:
Description: 'Bottlerocket updater container image'
Type: String
Default: 'public.ecr.aws/bottlerocket/bottlerocket-ecs-updater:v0.1.0'
Default: 'public.ecr.aws/bottlerocket/bottlerocket-ecs-updater:v0.2.0'
LogGroupName:
Description: 'Log group name for Bottlerocket updater logs'
Type: String
Expand Down