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
alibabacloud: use NextToken and MaxResults to list instance types #25387
alibabacloud: use NextToken and MaxResults to list instance types #25387
Conversation
08548ec
to
b7adf02
Compare
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.
Thanks for the PR!
I've left one comment and I have an overarching question: how does this change resolve the error you experienced? I'm not sure I follow why this fixes it.
/test |
ba4954b
to
0e45bc1
Compare
0e45bc1
to
b91fadb
Compare
/test |
This pull request has been automatically marked as stale because it |
Hi @christarazi @sayboras , please help to see if this PR can be merged. |
@haozhangami Could you rebase on PR on latest |
b91fadb
to
bdd47e1
Compare
Done |
Currently, there is no paging query used to retrieve instance types. When there are many instance types, some instances can not obtain ENI and IPPerENI limits. The cilium operator log is as follows. ``` level=warning msg="Unable to maintain ip pool of node" error="Unable to determine limits" instanceID=<ID> name=<NAME> subsys=ipam ``` This patch fixes this problem by using NextToken and MaxResults for paging query. Signed-off-by: Hao Zhang <hao.zhang.am.i@gmail.com>
bdd47e1
to
803e52e
Compare
/test |
Currently, there is no paging query used to retrieve instance types. When there are many instance types, some instances can not obtain ENI and IPPerENI limits. The cilium operator log is as follows.
This patch fixes this problem by using NextToken and MaxResults for paging query.