By default, the Ingress Nginx Controller listens to all ConfigMaps in a cluster, and when the add-on starts, it loads all ConfigMap resources into memory. If too many ConfigMaps are created, the add-on will load an excessive number of resources during startup, resulting in high memory usage and triggering an OOM error.

Solution

Restrict the namespaces that the Ingress Nginx Controller listens to. Modify the startup parameter --watch-namespace=xxx-system, where the specified namespace is that of the current controller.

Warning

This solution causes the Ingress Nginx Controller to monitor Ingress resources only in the specified namespace. To use Ingress resources in multiple namespaces, deploy an Ingress Nginx Controller in each namespace and modify the startup parameter so that it listens only to the namespace where the controller is located.

Last updated: 2026.07.23 14:31:46

Public security network record in Beijing: No. 11010802032137