-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
kubeadm: begin polling for bootstrap cluster info immediately #48737
kubeadm: begin polling for bootstrap cluster info immediately #48737
Conversation
The previous behavior was to sleep for `constants.DiscoveryRetryInterval` (5 seconds) before the first request.
Hi @mattmoyer. 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 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. I understand the commands that are listed here. |
/ok-to-test |
/lgtm |
/approve
…On Mon, Jul 10, 2017 at 4:40 PM Kubernetes Submit Queue < ***@***.***> wrote:
[APPROVALNOTIFIER] This PR is *NOT APPROVED*
This pull-request has been approved by: *justinsb
<#48737 (comment)>*,
*mattmoyer <#48737#>*
We suggest the following additional approver: *jbeda*
Assign the PR to them by writing /assign @jbeda in a comment when ready.
*No associated issue*. Update pull-request body to add a reference to an
issue, or get approval with /approve no-issue
The full list of commands accepted by this bot can be found here
<https://github.com/kubernetes/test-infra/blob/master/commands.md>.
Needs approval from an approver in each of these OWNERS Files:
- *cmd/kubeadm/OWNERS
<https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/OWNERS>*
You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#48737 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACRvtdwbDjVrQEMYilOMkRVsA3lJmFyks5sMrZegaJpZM4OThUU>
.
|
/test pull-kubernetes-e2e-kops-aws |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jbeda, justinsb, mattmoyer Associated issue requirement bypassed by: jbeda The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test pull-kubernetes-e2e-kops-aws |
Thanks @mattmoyer! No, this wasn't expected. Happy first contribution 👍 ! |
@mattmoyer Feel free to cherrypick this afterwards to the release-1.7 branch with the
|
Removing label |
Automatic merge from submit-queue |
@mattmoyer I added a release note to this, since that's required for a cherrypick |
@luxas - thanks for adding release note. Cherrypick approved. |
Commit found in the "release-1.7" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
What this PR does / why we need it:
This PR changes the behavior of the
kubeadm
loop that polls the API server waiting for discovery information (cluster-info
). The previous (inadvertent?) behavior was to sleep forconstants.DiscoveryRetryInterval
(5 seconds) before the first request (PollInfinite
vs.PollImmediateInfinite
).After this change,
kubeadm
begins does the first check immediately before it moves into the slower polling mode. This takes around 5 seconds off the average time for a new node to join.Before (~5.5s)
After (~0.5s)
Which issue this PR fixes:
Special notes for your reviewer:
This is my first Kubernetes PR, so please let me know if it's formatted correctly.
Release note: