Increase Node File Limit on a vSphere Kubernetes Cluster - Too many open files errors
search cancel

Increase Node File Limit on a vSphere Kubernetes Cluster - Too many open files errors

book

Article ID: 389709

calendar_today

Updated On:

Products

VMware vSphere 7.0 with Tanzu vSphere with Tanzu VMware vSphere Kubernetes Service Tanzu Kubernetes Runtime

Issue/Introduction

Applications/pods running on a node in a vSphere Kubernetes Cluster are encountering "Too many open files" errors.

 

Environment

vSphere with Tanzu 7

vSphere with Tanzu 8

This issue can occur regardless of if this cluster is managed by Tanzu Mission Control (TMC) or not.

Cause

File limit has been reached on the affected node(s).

Resolution

Resolution

There is currently no support for adjusting node file limit in a vSphere Kubernetes Cluster.

The ability to configure file limits at the cluster-wide level, which will apply to both existing and new nodes, will be added in a future release.

 

Workaround

Please reach out to VMware by Broadcom Technical Support referencing this KB article for assistance in manually increasing the file limit on the affected node(s).

Note: This change will be reverted on node recreation or reboot.