-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
don't wait for first kubelet to be ready and drop dummy deploy #43835
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -44,7 +44,7 @@ func CreateClientAndWaitForAPI(file string) (*clientset.Clientset, error) { | |
fmt.Println("[apiclient] Created API client, waiting for the control plane to become ready") | ||
WaitForAPI(client) | ||
|
||
fmt.Println("[apiclient] Waiting for at least one node to register and become ready") | ||
fmt.Println("[apiclient] Waiting for at least one node to register") | ||
start := time.Now() | ||
wait.PollInfinite(kubeadmconstants.APICallRetryInterval, func() (bool, error) { | ||
nodeList, err := client.Nodes().List(metav1.ListOptions{}) | ||
|
@@ -55,20 +55,11 @@ func CreateClientAndWaitForAPI(file string) (*clientset.Clientset, error) { | |
if len(nodeList.Items) < 1 { | ||
return false, nil | ||
} | ||
n := &nodeList.Items[0] | ||
if !v1.IsNodeReady(n) { | ||
fmt.Println("[apiclient] First node has registered, but is not ready yet") | ||
return false, nil | ||
} | ||
|
||
fmt.Printf("[apiclient] First node is ready after %f seconds\n", time.Since(start).Seconds()) | ||
fmt.Printf("[apiclient] First node has registered after %f seconds\n", time.Since(start).Seconds()) | ||
return true, nil | ||
}) | ||
|
||
if err := createAndWaitForADummyDeployment(client); err != nil { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we still need this check if the first node has already ready? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I suggest we move this and the node ready check to a seperate final validation step. Do you mean we should drop it permanently? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm, just noticed #43824 did this just after firstNodeIsReady There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think this is the right place to check that. Commented below. |
||
return nil, err | ||
} | ||
|
||
return client, nil | ||
} | ||
|
||
|
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.
Nit: you change this comment but don't fix up line 47. Most users won't parse registered vs. ready though.
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.
Fixed