Kind

Fleeting

kind, a local k8s

known issues

too many open files

• Référence externe : https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files Pod errors due to “too many open files”

  This may be caused by running out of inotify resources. Resource limits are defined by fs.inotify.max_user_watches and fs.inotify.max_user_instances system variables. For example, in Ubuntu these default to 8192 and 128 respectively, which is not enough to create a cluster with many nodes.

  To increase these limits temporarily run the following commands on the host:

$ sudo sysctl fs.inotify.max_user_watches=524288 $ sudo sysctl fs.inotify.max_user_instances=512

To make the changes persistent, edit the file /etc/sysctl.conf and add these lines:

fs.inotify.max_user_watches = 524288 fs.inotify.max_user_instances = 512

— https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files

Notes pointant ici

• clk k8s
• how I debug MTU issues in k3d in docker in earthly in docker in k8s (blog)
• how I debug my k8s tests not running
• investigate too many open files
• kind configure local registry with kube-public local-registry-hosting
• use kind and k3d with tilt and clk k8s
• with docker desktop (blog)

Permalink