Skip to content
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.

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

End to End Integ Test #10

Closed
webern opened this issue Dec 21, 2020 · 1 comment
Closed

End to End Integ Test #10

webern opened this issue Dec 21, 2020 · 1 comment
Assignees
Labels
priority/p0 Must have
Milestone

Comments

@webern
Copy link
Contributor

webern commented Dec 21, 2020

Create an end-to-end integ test that, with minimal human intervention. General requirements:

  • Use a pre-existing ECS cluster.
  • Detect pre-existing instances in the cluster and abort with error informing the user that the cluster should be empty.
  • Create multiple nodes taking a Bottlerocket AMI (version < latest), or getting it from SSM.
  • Create a workload service and run it on the nodes.
  • Assert health of the workload throughout test?
  • Containerize and deploy the local changeset version of bottlerocket-update-operator to an ECR repo.
  • Run the updater in a Fargate task.
  • Assert the nodes do update.
  • Cleanup.
@webern webern mentioned this issue Dec 21, 2020
13 tasks
@jhaynes jhaynes added this to the GA milestone May 11, 2021
@jhaynes jhaynes added the priority/p0 Must have label May 21, 2021
@srgothi92
Copy link
Contributor

In PR-68 and PR-69 we added Cloudformation stacks to create an ECS cluster and added script that allows us to create an ECS cluster, start updater on it and clean-up the resources. For now we are relying on manual validation of logs and Bottlerocket OS version. An issue #76 is created to track automated integration tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/p0 Must have
Projects
None yet
Development

No branches or pull requests

3 participants