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


---

# Enable service maps using DaemonSet

# Enable service maps using DaemonSet {#ariaid-title1}

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

Enable application service maps based on the traffic between the workloads in Kubernetes by using a ServiceNow DaemonSet as part of Kubernetes Visibility Agent (KVA) installation.

## Before you begin

Role required: discovery_admin.

## About this task

If you use a ServiceNow DaemonSet, a pod is running on each Kubernetes node and reports to the main Informer pod every 60 seconds on new connections detected. For more information, see [Install Kubernetes Visibility Agent (KVA) Informer](https://servicenow-prod.fluidtopics.net/skfDBD8ABVoxV9UUc3EX3Q "You can install Kubernetes Visibility Agent Informer using either a Helm chart or the Kubernetes YAML file.")

## Procedure

Set parameters either during Helm chart archive installation or by modifying the Kubernetes YAML file provided by ServiceNow.

| Method | Actions |
| During Helm chart archive installation | 1. In the Helm `install` command, add the following parameter: --set connectionsDiscovery.method=servicenow 2. If your organization's policy requires it, pull the DaemonSet image from Docker hub and place it in your organization's image repository.Replace the placeholder X characters with the number of the most recent release provided in the [Kubernetes Visibility Agent (formerly CNO for Visibility) Helm Chart and Kubernetes YAML file releases \[KB1564347\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1564347) article in the Now Support Knowledge Base. Docker pull servicenowdocker/informer_ds:X.X.X Docker tagservicenowdocker/informer_ds:X.X.X COMPANY_REPO:X.X.X 3. In the `Helm install` command, add the following parameters: `--set image.dsRepository=COMPANY_REPO --set image.dsTag=X.X.X` {#create-service-maps-using-daemonset__ol_wfz_f5k_bgc} |
| Modifying the k8s_informer.yaml file | 1. In the k8s_informer.yaml file, uncomment the DaemonSet, ServiceAccount (used by the DaemonSet), and Service.Deployment resources according to the instructions in the file. 2. Uncomment the lines containing environment variables. 3. If your Prometheus server URL isn't the default one, uncomment the lines containing the environment variable <var class="keyword varname">PROMETHEUS_URL</var> and change the value. 4. Run the following command: kubectl apply -f k8s_informer.yaml {#create-service-maps-using-daemonset__ol_c5g_f5k_bgc} |
|-|-|

{#create-service-maps-using-daemonset__choicetable_ucg_fpk_bgc}

## What to do next

[Create application service maps](https://servicenow-prod.fluidtopics.net/eK~KGuIlJG1OmWEeQzo6RA "Create a service map that maps application services based on traffic between the workloads in Kubernetes using Istio or Linkerd service meshes or a ServiceNow DaemonSet.")