---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure memory limit and memory request

# Configure informer pod memory limit and memory request {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Set the memory limit and memory request of the Kubernetes Visibility Agent Informer pod.

## Before you begin

Role required: none

## About this task

Informer pod memory consumption depends mainly on the number of resources contained in the cluster. Memory limit defines the maximum memory the informer container is allowed to use, while memory request defines how much
memory to reserve when scheduling the informer pod. Set the Informer pod's memory request and the Informer pod's memory limit to at least (number of pods)/8MB, with a default minimum of 200MB. Memory request must not exceed
the memory limit. For example:  
{#cnov-config-informer-memory__table_mcf_qbz_syb__entry__4}

|   |   |   |   |
|-|-|-|-|
| Estimated pod count | 1000 | 5000 | 30000 |
| Minimum memory limit | 200Mi | 625Mi | 3.75Gi |
| Memory request | 200Mi | 625Mi | 3.75Gi |
[Table 1. Informer pod memory requirements]

{#cnov-config-informer-memory__table_mcf_qbz_syb}

## Procedure

Do one of the following:

* When using a Helm chart, in the Helm install command, add the following command line arguments:

      --set memoryLimit=MEM_LIMIT\
      --set memoryRequest=MEM_REQUEST

  For example:

      --set memoryLimit=625Mi\
      --set memoryRequest=625Mi

* When using the k8s_informer.yaml, under the line containing "limits:" add the line `memory: MEM_LIMIT`.  
  In the following example, MEM_LIMIT and MEM_REQUEST are 625Mi.


        limits:
          cpu: 100m
          memory: 625Mi
        resources:
          cpu: 100m
          memory: 625Mi

  Note:  
  Setting `memoryRequest` equal to `memoryLimit` reserves exactly the memory your ACC agent needs. It prevents the ACC agent from being shut down if the system runs low on memory.
  This guarantees stable, uninterrupted agent operation. If you leave memoryRequest at the default 200Mi while setting a higher memoryLimit (such as 625Mi), the pod is burstable. It schedules against 200Mi but
  can grow to 625Mi.
{#cnov-config-informer-memory__choices_cjl_2jz_syb}