---
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 server CI creation for Kubernetes nodes

# Configure server CI creation for Kubernetes nodes {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure whether the Kubernetes Visibility Agent Informer creates a server CI for each Kubernetes node.

## Before you begin

Role required: none

## About this task

By default, the Informer creates a server CI for every Kubernetes node: a Linux Server \[cmdb_ci_linux_server\] CI for each Linux node and a Windows Server \[cmdb_ci_win_server\] CI for each Windows node. Both CI types have the same fields populated. If a matching
virtual machine was already discovered, for example by Cloud Discovery or a Service Graph connector, the Informer relates the server CI to the VM Instance \[cmdb_ci_vm_instance\] CI. If these CIs are redundant or interfere
with other flows in your organization, you can set the associated configuration parameter to false.  
Note:  
The Informer doesn't create a server CI for a node that represents an AWS Fargate profile in an Amazon EKS cluster.

## Procedure

Do one of the following:

* When using a Helm chart, in the Helm install command, set the createServerCi parameter to false:

  `--set createServerCi=false`
* When using the k8s_informer.yaml file, set the environment variable CREATE_SERVER_CI to false.
{#cnov-config-linux-server-ci__choices_oz5_fwd_51c}