-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
stuck when creating a cluster by kind #3683
Comments
Please fill in the requirement info from the issue template as this is more than likely something specific to your environment and it will be hard to diagnose otherwise.
Though I do see you mention you are running kind v0.17.0. That is a quite old version at this point, and I would not be surprised if it no longer works reliably. So my first suggestion would be to upgrade to the latest release and use a newer version of k8s if possible. v1.25.3 is quite old as well at this point. |
Hello, I updated my Environment part, thanks for your reply! |
I updated my kind version to 0.23.0,my environment is as follow:
After I updated, I run
What should I do now, thanks for any help. |
do you have enough resources as in RAM memory and CPU? |
I run
|
do you have the image locally |
This isn't working because you're using an outdated image, please see the release notes and the note in the quickstart guide about image selection. |
That image was published with kind v0.17, there have been major changes since then noted in the release notes. |
To expand on that, in the v0.23.0 release under the New Features heading you can see a list of the supported versions. v1.25.16 is still supported by kind, but that k8s release in general is no longer supported upstream. So I would recommend moving to a newer one if at all possible. To do a little more validation of your environment, after installing the latest kind version, I would recommend just running a plain Then you could try If both of those work, only then would I add in your configuration file to try to set up the full cluster config you are trying to use. If that fails you already know most of the basics are fine from those previous steps, so that will narrow down where the failure could be coming from and hopefully make it easier to focus your troubleshooting to find the root cause of the failure. You didn't add the I've also had strange issues in the past where I needed to clean up my Docker environment with a I'm also unsure of AliOS. I've never used it, but from what I understand it is sort of a fork of Android? If so, there may be some other challenges with using kind here. But some of the above steps can help to see if that is a problem. |
Yes, I have the image locally |
Thanks, I'll try latest version. |
I'm going to close this since it doesn't seem to be anything that requires action on the kind side. But it would be great to hear if updating to a newer image worked for you. If you did update but it did not solve your issue, please feel free to reopen and add more details. /close |
@stmcginnis: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
what happened
I tried to create a cluster by kind, it went well before i met this:
Then I waited for hours, it's still the same.
So next time when I'm creating a kind cluster, I used
kind export logs
in another command line window to see what's going on.but the process of exporting log is stuck too:I checked
/tmp/1019242815/kind-worker/alternatives.log
(the only file except kind-version.txt)Here's the log content:
Then I run
top -u admin
:It turns out no process is running,
What i expected to happen:
Cluster can be created successfully.
How to reproduce it
My kind-cluster.yaml:
Run
kind create cluster --image kindest/node:v1.25.3 --config kind-cluster.yaml
Environment:
no special environment settings
Thanks for any help
The text was updated successfully, but these errors were encountered: