Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
dnsmask failed to create inotify #2709
kops version: 1.6
Here are the logs we saw:
We upgraded the cluster, and the error is gone.
This looks like related to: kubernetes/kubernetes#32526
Kops indeed has this setting on the node:
Would it be beneficial to update this number? We can PR if necessary?
As a side note, since the beginning of the cluster, I can't tail pods logs with this error message:
I'm not sure it is related, but I though it is worth to mention.
As a second side note, inodes there are 4.33M free inodes.
referenced this issue
Jun 12, 2017
Just for information, in order to finish upgrade we had to kill failing pod each time after next node were recreated. Since cops were reporting
Once failing pod deleted, rolling update can be started again.
Does updating this number fix the issue? We support a bunch of different operating systems and I am uncertain which OS's this impacts.
If we can figure out a solution, please PR ;)