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
WINC-956: Reduce direct use of the AWS API in e2e tests #1365
Conversation
/test aws-e2e-operator |
Skipping CI for Draft Pull Request. |
/test aws-e2e-upgrade |
/approve cancel |
@sebsoto Thanks for working on this. It looks like throttling on AWS disproportionately affects WMCO PRs. |
/test aws-e2e-operator |
/test aws-e2e-upgrade |
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.
Thanks for doing this, @sebsoto
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aravindhp 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 |
This commit brings the AWS provider in line with the rest of the providers, by using an existing worker MachineSet as a base for the Windows MachineSet created in our e2e tests. This removes complexity related to dealing with the AWS CLI, simplifying the provider code, and reducing the potential of test failure due to AWS API rate limiting issues that can infrequently occur. The only remaining API call is DescribeImages, which is required as the use of the MachineAPI for AWS requires a specific imageID be provided.
`go mod tidy && go mod vendor`
/make lint |
/cherry-pick release-4.12 |
@sebsoto: once the present PR merges, I will cherry-pick it on top of release-4.12 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.11 |
@sebsoto: once the present PR merges, I will cherry-pick it on top of release-4.11 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Thanks for working on this, |
/retest-required |
1 similar comment
/retest-required |
/retest-required
|
/test aws-e2e-upgrade |
/retest-required |
@sebsoto: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@sebsoto: new pull request created: #1374 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@sebsoto: #1365 failed to apply on top of branch "release-4.11":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR brings the AWS provider in line with the rest of the providers, by using an existing worker MachineSet as a base for the Windows MachineSet created in our e2e tests. This removes complexity related to dealing with the AWS CLI, simplifying the provider code, and reducing the potential of test failure due to AWS API rate limiting issues that can infrequently occur.
The only remaining API call is DescribeImages, which is required as the use of the MachineAPI for AWS requires a specific imageID be provided.