-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Refactoring the provider to unit test create cluster #5259
Conversation
4dbbfc2
to
e4b8ee1
Compare
74d3ca5
to
c264a78
Compare
c264a78
to
0899701
Compare
Integration tests passed except for a single test which timed out on TLS. That appears to be a fluke from AWS though. I'm running it locally to verify that. Edit: Works:
|
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.
Just one comment about considering embedding KubeProvider
, but otherwise LGTM.
My deadline-based Context PR will result in conflicts, so I'll wait for this to be merged before merging mine.
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.
LGTM 👍🏻
Description
Ground work for #5015.
What happens in this PR?
Provider
toAWSProvider
since it provides AWS functionalityIntegration test run https://github.com/weaveworks/eksctl-ci/actions/runs/2330469236
edit: New test run https://github.com/weaveworks/eksctl-ci/actions/runs/2332032290
Checklist
README.md
, or theuserdocs
directory)area/nodegroup
) and kind (e.g.kind/improvement
)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯