bottlerocket-ecs-updater
bottlerocket-ecs-updater copied to clipboard
bottlerocket-os
A service to automatically manage Bottlerocket updates in an Amazon ECS cluster.
This looks odd: For v0.2.3, the stack lists a tag for the version previous. I assume that a releases == new tags in ECR https://github.com/bottlerocket-os/bottlerocket-ecs-updater/blob/v0.2.3/stacks/bottlerocket-ecs-updater.yaml#L13 So it hsould be `public.ecr.aws/bottlerocket/bottlerocket-ecs-updater:v0.2.3`...
**What I'd like:** I would like to start the updater on one of the instances of my cluster, so that I can reduce the cost of running the updater. Important...
- [x] List container instances in the cluster that are running Bottlerocket. (https://github.com/bottlerocket-os/bottlerocket-ecs-updater/issues/5) - [x] Keep only those that need a Bottlerocket update. (Checking this can be done in parallel.)...
**What I'd like:** Automated integration tests that can: * Create an ECS cluster with Bottlerocket instances * Run the updater on the cluster. * After updater is done, assert Bottlerocket...
**What I'd like:** `cluster.yaml` stack template currently expects AMI-ID to launch Bottlerocket instances. Easier user interface would be to just provide Bottlerocket version and stack can fetch the AMI-ID using...
**What I'd like:** Implement a logging mechanism to improve Updater's logging output in lieu of relying on `log.Printf` statements. Potential candidates: https://pkg.go.dev/github.com/sirupsen/logrus https://pkg.go.dev/go.uber.org/zap
**What I'd like:** Currently Updater operates under the assumption that it is the only actor manipulating the instances to DRAINING or ACTIVE. In situations where this is not true instance...
> Instead you could create a new type `Instance`, i think which I suggested somewhere else and maintain a list of this type whose items gets modified/deleted/added throught the update...
Metadata
Owner
Metadata
A service to automatically manage Bottlerocket updates in an Amazon ECS cluster.