Makes GCE manager handle createInstances call of more than 1k instances#9315
Conversation
|
Hi @pmendelski. 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. |
|
cc @x13n |
|
/ok-to-test |
cluster-autoscaler/cloudprovider/gce/autoscaling_gce_client_test.go
Outdated
Show resolved
Hide resolved
|
/assign damikag |
jbtk
left a comment
There was a problem hiding this comment.
Is there any further plan to use it? Can you provide more context?
08e782d to
3386514
Compare
|
/lgtm |
3386514 to
9e8e584
Compare
9e8e584 to
955363a
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pmendelski, x13n 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 |
|
/retest |
955363a to
8ed1230
Compare
|
Awaits e2e test fix #9470 |
|
e2e test fix was merged, can you rebase? |
When there are multiple `createInstances` requests sent in a sequence, the next request must be aware of the instance names used by the previous request. Without this change sending a sequence of create instances requests would result in the instance name duplication error.
8ed1230 to
d544b6c
Compare
|
e2e test /retest |
|
/lgtm |
|
Test passed, PR type changed to feature and added release note |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Makes GCE manager handle createInstances call of more than 1k instances.
Single
createInstancesGCE call is limited to 1000 instances. It's enforced in GCE validation.GCE manager sends a sequence of request to overcome this limitation.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: