-
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
local-up-cluster.sh always fail with "Timed out waiting for apiserver" #49319
Comments
@mtanino
Note: Method 1 will trigger an email to the group. You can find the group list here and label list here. |
I've noticed that If you revert the change, once the cluster is started curling the healthz in https works
It might be a waiting problem? Maybe the API server takes longer to setup |
The patch applied following two fixes. Seems extending wait time fixes my original problem on #47739, but I'm not sure why API endpoint was changed to https.
|
Since hack/local-up-cluster.sh checks https API port after commit 413ab26, RBAC should be enabled by default to avoid TLS port access denied. Fixes kubernetes#49319
/sig cluster-lifecycle |
Automatic merge from submit-queue (batch tested with PRs 49316, 46117, 49064, 48073, 49323) Enable RBAC by default in hack/local-up-cluster.sh **What this PR does / why we need it**: Since hack/local-up-cluster.sh checks https API port after commit 413ab26, RBAC should be enabled by default to avoid TLS port access denied. **Which issue this PR fixes** : Fixes #49319 **Special notes for your reviewer**: @liggitt **Release note**: ```release-note hack/local-up-cluster.sh now enables RBAC authorization by default ```
Since hack/local-up-cluster.sh checks https API port after commit 413ab26, RBAC should be enabled by default to avoid TLS port access denied. Fixes kubernetes#49319
Since hack/local-up-cluster.sh checks https API port after commit 413ab26, RBAC should be enabled by default to avoid TLS port access denied. Fixes kubernetes#49319
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
#49072
What happened:
After this commit was introduced, local-up-cluster.sh always fail with "Timed out waiting for apiserver" error.
I'm not sure the reason but the local-up-cluster.sh successfully start if I specify ENABLE_RBAC=true option to local-up-cluster.sh.
What you expected to happen:
The local-up-cluster.sh will successfully start without any additional options.
How to reproduce it (as minimally and precisely as possible):
The text was updated successfully, but these errors were encountered: