-
Notifications
You must be signed in to change notification settings - Fork 234
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
Use smaller instances for AWS E2E tests #2415
Conversation
/retest |
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
9635a86
to
5e94ea1
Compare
/test pull-kubeone-e2e-aws-default-stable-upgrade-containerd-from-v1.23.13-to-v1.24.7 |
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
5e94ea1
to
14c0fd2
Compare
/test pull-kubeone-e2e-aws-default-stable-upgrade-containerd-from-v1.23.13-to-v1.24.7 |
1 similar comment
/test pull-kubeone-e2e-aws-default-stable-upgrade-containerd-from-v1.23.13-to-v1.24.7 |
/retest |
1 similar comment
/retest |
d4c8f13
to
14c0fd2
Compare
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
181a39a
to
ee48d5d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
LGTM label has been added. Git tree hash: b7409c9b46029ad1468f0d2940ef4f724ebeb1b7
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
1 similar comment
/retest |
What this PR does / why we need it:
This PR introduces the following changes to the AWS E2E tests:
eu-west-1
)t3a.small
for the control plane and worker nodest3a
instances are slightly slower thant3
instances, but they're also cheaper. This doesn't seem to affect the speed of E2E tests at allt3a.micro
instances for worker nodes in the upgrade testst3a.nano
(t3.micro
for RHEL) instead oft3.nano
for the bastion instanceOld setup:
eu-west-3
)t3.medium
andt3.nano
instancesDisclaimer: the following table doesn't take into account other cloud resources.
New setup:
eu-west-1
)t3a.small
andt3a.nano
instancesDisclaimer: the following table doesn't take into account other cloud resources and using spot instances for the worker nodes.
Savings per job/hour: $0,1616
Savings per run/hour: $0,6464
Considered:
t3.micro
, but it only has 1 GB RAM which is not enough for running the conformance tests. All tests were failing.What type of PR is this?
/kind chore
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: