-
-
Notifications
You must be signed in to change notification settings - Fork 139
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
Autoscaled nodes not joining cluster #466
Comments
Hi, can you share your full config file (minus the token)? |
|
Hi, this has been reported a couple of times before but I haven't had a chance to try and reproduce the problem yet. Can you share more details on how you have configured the network in Hetzner? The more details the better as they might help me understand where the problem might be. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
We are running Hetzner-k3s version 2.0.8 with the following worker pool config:
The nodes are created in Hetzner after autoscaling is initiated by stressing the cluster but they are not joining the cluster after that. We can ssh into the machines but they don't have for example ssh keys set or anything related to k3s installed. For static nodes the ssh keys are set correctly.
We think this has something to do with the previous cloud init wait problem in issue #379
If we read the code correctly the cloud_init_wait.sh script is not called when creating a autoscaled node?
We are running a private network only cluster. Regarding to this PR #458 our cloud init takes several minutes with both static and autoscaled nodes.
The text was updated successfully, but these errors were encountered: