kamatera cloudprovider refactor, fixes, improvements#9740
Conversation
|
Hi @OriHoch. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
|
|
/lgtm |
|
@OriHoch: you cannot LGTM your own PR. DetailsIn 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-sigs/prow repository. |
|
/ok-to-test |
|
@OriHoch: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn 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-sigs/prow repository. |
|
/ok-to-test |
|
/triage accepted |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: OriHoch The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
this PR replaces #9123 which had some problems with rebasing and was accidentaly closed
What type of PR is this?
/kind bug
/kind cleanup
/kind feature
What this PR does / why we need it:
After running the Kamatera cloudprovider for some customers a few months this PR does a lot of fixes and improvements from feedback we got.
Special notes for your reviewer:
Changes were well tested using our internal end-to-end testing suite on Kamatera infrastructure. Also, many unit tests were added.
Does this PR introduce a user-facing change?