-
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
hack/local-up-cluster.sh broken on latest 1.5 branch #38847
Comments
Thanks for noticing this @janetkuo @kubernetes/sig-cluster-lifecycle can you please help investigate and triage this issue or help find the correct owner? We need to:
|
Update: #38708 is the cause |
CC @bprashanth Local cluster up is a "hack" script we provide. It sucks that it broke in v1.5.1, but we do not need to rush a fix a v1.5.2 out the door to fix it. Instead we will wait for the normal v1.5.2 release schedule (post holiday). Action items:
We need an owner for both these items. @janetkuo Could you own item 1? @deads2k Could you own item 2? |
Yes |
Yeah. I fixed it in a different pull once before |
Is the following workaround acceptable? Pass |
Thank you both.
|
Yeah, that's actually better than what I did with the modification I made. You want to do that instead? |
Filed #38884 |
Automatic merge from submit-queue Document known issue for broken local-up-cluster script in 1.5.1 Ref #38847
Automatic merge from submit-queue make local-up-cluster.sh match "normal" launch without anonymous access Ref #38847 This changes the readiness detection, but keeps the defaults matching the "normal" launch without anonymous auth. ```release-note Fixes an issue where `hack/local-up-cluster.sh` would fail on the API server start with !!! [1215 15:42:56] Timed out waiting for apiserver: to answer at https://localhost:6443/version; tried 10 waiting 1 between each ``` @janetkuo @saad-ali
I can confirm that without @janetkuo's suggested fix, local-up-cluster doesn't actually produce a functioning cluster. Controller manager is blocked from accessing anything. |
Well, let me back off on that claim. The controller manager seems to be able to talk to apiserver again, but pods don seem to be able to.
e.g. etcd-operator prints a stream of the above. |
I think the issue is that the apiserver is failing to give the kubernetes service any endpoints. |
|
OK, I figured it out.
should be:
because the API_HOST variable is "localhost", not 127.0.0.1. |
Automatic merge from submit-queue Actually fix local-cluster-up on 1.5 branch Fixes #38847 (for real)
This ought to be fixed now. |
local cluster failed to start in the latest 1.5 branch (commit 09cb1a9):
The text was updated successfully, but these errors were encountered: