-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Kubernetes hyperkube infinte secrets mounts #26864
Labels
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
Comments
This looks like a dupe of #25489 |
This was referenced Jun 10, 2016
and of #26996 |
This is a dupe, yes. Fundamentally the problem is that the mount point isn't propagating back into the mount ns of the container where the hyperkube process is running. |
I think #27054 should fix the issue of infinite (thousands) mounts |
yujuhong
added
team/cluster
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
and removed
sig/node
Categorizes an issue or PR as relevant to SIG Node.
labels
Jul 26, 2016
Closing. We believe 1.3.4 addresses this. Re-open if we are mistaken. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm experiencing a very slow behaviour of my Kubernetes cluster. Evrything starts OK, but passed hours everything starts to be very very slow.
I've noticed that executing "mount" I can see nearly infinite (thousands) mounts like these ones:
Also, there seems to be a process called "findmnt" running:
I'm using:
I've tried to upgrade to:
but the result was the same :(
I've also tried to run Kubernetes directly using the kubelet binary, outside Hyperkube, and everything seemed OK, no more infinite mounts, and good speed, but everything was planned to use Hyperkube, and also I really want to know what is going wrong.
The text was updated successfully, but these errors were encountered: