---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Override Informer parameters from the Instance

# Override Informer parameters from the Instance {#ariaid-title1}

* Release version: Yokohama
* 
* Updated May 21, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Control Kubernetes Visibility Agent Informer execution parameters from the ServiceNow Instance to avoid dependence on your Kubernetes admin.

## Before you begin

Role required: discovery_admin

## About this task

The Informer execution parameters are configured during deployment using the Kubernetes Yaml file or the Helm command. If you need to change these settings later, you can do so directly from the Instance without having to ask your Kubernetes team to update or reinstall the deployment.

When you add or modify a parameter, it is synchronized with the informer through the ECC Queue. Depending on the parameter, the Informer pod may need to restart. Parameters requiring a restart must have the
SELF_PATCHING_ALLOWED environment variable set to true for changes to be effective upon restart. If this variable is set to false, the Informer is not restarted and continues to use the old values.  
Note:  
Informer-specific parameters only affect a specific Informer. If you add a parameter without assigning it to an Informer, it defaults to a global parameter and affects all Informers in the system. When both global and Informer-specific parameters are present, Informer-specific parameters take precedence.  
You can update the following parameters from the Instance:{#cnov-params-override__table_u24_2fw_1cc__entry__2}

| Parameter | Restart upon change |
|-|-|
| VERBOSE_LOGGING | No |
| OPENSHIFT | Yes |
| CREATE_SERVER_CI | No |
| INCLUDE_LABELS_AND_ANNOTATIONS | No |
| EXCLUDE_LABELS_AND_ANNOTATIONS | No |
| FULL_DISCOVERY_MIN | Yes |
| SEND_INTERVAL_SEC | Yes |
| CONTINUOUS_DISCOVERY | Yes |
| CLUSTER_RESOURCE_ID | No |
| CLUSTER_NAME | No |
[ ]

{#cnov-params-override__table_u24_2fw_1cc}

The CREATE_CONTAINERS parameter determines which Docker containers are deployed to the instance. It is managed automatically and is not exposed in the Configuration Parameters
list. A new system property, sn_itom_pattern.bring_discovery_container, which is available when the Discovery and Service Mapping Patterns plugin is installed, governs
CREATE_CONTAINERS automatically. When sn_itom_pattern.bring_discovery_container is set to <kbd class="ph userinput">true</kbd> (default), CREATE_CONTAINERS is set to
`non-init-containers`. When set to <kbd class="ph userinput">false</kbd>, CREATE_CONTAINERS is set to `none` and no Docker containers are brought to the instance. Each change
triggers the ECC Queue sync to propagate the updated value with the Informer.

For information about the purpose of each parameter, see the [Kubernetes Visibility Agent (formerly CNO for Visibility) Advanced Configuration Options \[KB1648891\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1648891) article in the Now Support Knowledge Base.

## Procedure

1. Navigate to AllKubernetes Visibility AgentConfiguration Parameters.
2. Select a parameter in the Kubernetes Informer Parameters list.
3. Change the configured value as needed, and then select Update.

*[\>]: and then