generated from siderolabs/project-template-kubernetes-controller
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Bootstrap request to first cpn takes a long time #133
Comments
@Unix4ever any ideas? |
A few updates in case it's helpful.
Here's how I'm creating the docker management cluster:
with the patch file being
|
Are you using latest versions of the providers? We had some fixes since that time. |
Yes - I am using the latest released versions of the providers.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Might be the same as #109.
I'm creating a cluster on some old Dell R620s with sidero and am noticing that once the first control plane node gets to the point where it needs to receive the bootstrap request, it takes a variable amount of time to receive it. I've seen between 6 and 15 minutes. If I kill the cacppt-controller-manager pod, that seems to kickstart things.
I'm running the latest of everything.
Attached is the cacppt-controller-manager log. This log has two cluster provisions, with the first one not having the "takes a long time" issue, and the second one experiencing the issue. I think the interesting bits start at 1.658505243132774e+09 (last failed message).
cacppt-controller-manager-delayed-bootstrap.txt
cpn_console.txt
The text was updated successfully, but these errors were encountered: