Change vm.max_map_count on worker nodes
Article ID: 403381
Updated On:
Products
Issue/Introduction
Application deployments to VKS clusters may fail due to incompatibilities between the default value for the vm.max_map_count and the required value for the application.
Similar errors may be triggered during deployment:max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [######]
Environment
VKS 3.5.0
Cause
The default vm.max_map_count for VKS clusters, 65530, is too low for the associated application to complete installation
Resolution
Broadcom is looking to support updating this value in a later release of vSphere Kubernetes Services (VKS)
As a workaround, a new cluster class can be created and the VKS deployed using that cluster class to apply the vm.max_map_count value.
See the following documentation for custom cluster class: Example: Cluster Based on a Custom ClusterClass with TKG Service 3.2.0 and Later
Additional Information
Please see the following guidance if using Tanzu Kubernetes Grid deployments:
Update kernel parameter for Elasticsearch on TKGi Cluster.
Tanzu Kubernetes Grid 2.5 - Create a Custom ClusterClass
Feedback
