-
Notifications
You must be signed in to change notification settings - Fork 578
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
✨ refactor: cluster scope and service refactor for future EKS support #1810
✨ refactor: cluster scope and service refactor for future EKS support #1810
Conversation
Hi @richardcase. 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/test-infra repository. |
A slight refactor of the `ClusterScope` so that the ec2 service can be reused by the EKS implementation. Relates To: #1796
/ok-to-test |
Fixed an issue where the metrics change to the AWS clients had been lost. Also added comments to the new ClusterScoper interface. Issue: #1796
FWIW built this into an image and rolled it out to an existing self-managed cluster. Tested a handful of Machine/AWSMachine operations and saw no issues! |
The networking parts of the ec2 service have been split into a new `network` service. As part of this the ClusterScoper interface has been trimmed down and scopes specific to the ec2 and new network services have been introduced. Relates to: #1796
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: randomvariable 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 this PR does / why we need it:
A slight refactor of the
ClusterScope
related stuff so that the ec2 service can be reused by the EKS implementation. Specifically in the future there will be aAWSManagedCluster\AWSManagedControlPlane
.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 #1796