---
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


---

# Create a cmdb_ci_linux_server CI for each Kubernetes node

# Create a cmdb_ci_linux_server CI for each Kubernetes node {#ariaid-title1}

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

Configure if you want the Kubernetes Visibility Agent Informer to create a cmdb_ci_linux_server CI for each Kubernetes node.

## Before you begin

Role required: none

## About this task

By default, the Informer creates a cmdb_ci_linux_server CI for every Kubernetes node. If this CI is redundant or interferes with other flows in your organization, you can set the associated configuration parameter to false.

## 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}

