-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Can't create second kind cluster #3712
Comments
We need the https://kind.sigs.k8s.io/docs/user/known-issues/ this is almost always a resource exhaustion issue with the host such as https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files Which you can tell by it only being additional clusters that don't work. Clusters don't otherwise interact. |
I adjust inotify resource setting, but it does'n work. |
the logs of the working cluster are not going to help much, you need to run the second cluster with the flag |
The 4.x kernel raises some concern. Is this an older release of Amazon Linux? The output from |
that command is per cluster, it takes a --name flag (most do) |
@stmcginnis It's an instance from another cloud provider. The following is the output of
|
@BenTheElder Thanks. |
Because kubelet.log is too big. I only attach the start and end part.
Endding 20 lines
|
it looks like this kubernetes/kubernetes#122955 |
@aojea Thanks, I'll go take a look. |
I tried to create two clusters using kind. But it seems something unexpected happen. I I've looked up some of the current issues, but they don't seem to be quite the same as mine.
The first cluster works fine and the second encounter some problems.
Error Log
The following is the log of creating second cluster.
Acutally it seems everything is fine. But I don't know why apiserver keeps not ready.
local enviroment
Memory 16Gi
kind version: 0.22.0
uname -r: 5.10.134-16.3.al8.x86_64
docker version
The text was updated successfully, but these errors were encountered: