-
Notifications
You must be signed in to change notification settings - Fork 90
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
Increase timeout for apiserver check #2362
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @whiterm. Thanks for your PR. I'm waiting for a aws 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. |
Thanks for the contribution! Can you give me a bit more about your setup? Do you have a LB that is being provisioned during the cluster creation process, is that where |
@jaxesn |
What is the |
@jaxesn
|
Awesome, thanks for the info! What is configuring the LB to have the newly created CP node IPs? Is that something you are running externally to create cluster process? |
@jaxesn |
Issue #, if available:
Description of changes:
These changes increase the timeout for apiserver check. The old check with a 30 second timeout after one failed attempt immediately crashes during installation. In a configuration with loadbalancer, 30 seconds before apiservers is not enough.
The new behavior will try to check apiserver at least 5 times.
Error from enviroment with loadbalancer:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.