-
Notifications
You must be signed in to change notification settings - Fork 629
✨ Migrate EKS packages to AWS SDK v2 #5498
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
✨ Migrate EKS packages to AWS SDK v2 #5498
Conversation
Hi @punkwalker. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
/ok-to-test |
2c09599
to
7db7dd1
Compare
/test pull-cluster-api-provider-aws-test |
848c7c5
to
d6de30f
Compare
/test pull-cluster-api-provider-aws-e2e-eks |
1 similar comment
/test pull-cluster-api-provider-aws-e2e-eks |
/retest |
pkg/cloud/services/eks/eks.go
Outdated
|
||
const ( | ||
// Maximum duration for waiting on EKS cluster state. | ||
maxActiveUpdateDeleteWait = 15 * time.Minute |
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.
Should we make this configurable?
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.
@richardcase Sure. Do you have any opinion on where this should be configurable? As a flag or a field in the AWSManagedControlPlane type?
I feel it should be a field in the type, same way we can have a field for AWSManagedMachinePool.
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.
I would've said flag :) Depends if we want it global or set per cluster. I can't imagine we'd want to change it per cluster....but i could be wrong?
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.
We can go with flag, as the value really doesn't matter in happy case. So I will make it a flag which can be used with ControlPlane, MachinePool and Addon alike with 30mins default value. What do you think?
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.
Added the flag. Please check @richardcase
/test pull-cluster-api-provider-aws-e2e-eks |
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
…EKS resource creation to be ready Signed-off-by: Pankaj Walke <[email protected]>
a960b88
to
8e113d9
Compare
Signed-off-by: Pankaj Walke <[email protected]>
6156782
to
9ecc240
Compare
/test pull-cluster-api-provider-aws-e2e-eks |
/lgtm |
LGTM label has been added. Git tree hash: 9ca18d0d176eedc769754960aa1f1ca57a390700
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nrb 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 |
What type of PR is this?
/kind feature
/kind cleanup
What this PR does / why we need it:
max-wait-managed-resources
flag to specify maximum duration to wait for AWS managed resources to be ready. Currently it is respected by AWSManagedControlPlane, AWSManagedMachinePool and EKSAddons.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #5404
Special notes for your reviewer:
Part of AWS SDK V2 migration. Ref: #2225
Checklist:
Release note: