Inside the Kubernetes Visibility Agent: Real-Time CMDB Updates Made Simple

Insights and experiences from ServiceNow Knowledge 25 in Vegas, highlighting innovation, community, and the future of digital transformation with Agentic AI and automation.

Published on

Jul 14, 2025

Written by

Pratiksha Khandelwal

Category

ServiceNow

Kubernetes Visibility Agent

Let’s break down how the Kubernetes Visibility Agent functions, step by step, so you can clearly understand how it helps populate your CMDB in ServiceNow.
 
The Kubernetes Visibility Agent supports visibility into:  
  • On-premises Kubernetes clusters
  • Cloud-hosted Kubernetes services like:
    • Amazon EKS (Elastic Kubernetes Service)
    • Google GKE (Google Kubernetes Engine)
    • Microsoft AKS (Azure Kubernetes Service)
    • Red Hat
    • OpenShift
    • Rancher
  • This broad compatibility means you can monitor hybrid and multi-cloud environments from a single ServiceNow instance.
 
 
 
  1. Deployment in Kubernetes  
    • When you deploy the Kubernetes Visibility Agent, Kubernetes creates a Deployment resource inside your cluster.  
    • This Deployment is responsible for running the agent.  
    • To securely connect to your ServiceNow instance, it uses a Kubernetes secret that holds the necessary credentials.

  2. Role of the Informer Pod  
    • Inside this Deployment, a pod called Informer is created.  
    • The Informer plays a critical role - it connects to the Kubernetes API Server.  
    • It listens to events and changes happening across the cluster - like new pods, services, or nodes being added or removed.

  3. Sending Data to ServiceNow
    • Once the Informer collects this data, it sends it to ServiceNow.  
    • It does this by using the ServiceNow Table API to interact with the ECC Queue table (External Communication Channel).  
    • The ECC Queue acts as a communication channel between your Kubernetes cluster and the ServiceNow platform.  

  4. Updating the CMDB  
    1. After reaching the instance, the data is processed.  The appropriate CMDB tables are updated with the discovered Kubernetes resources - like clusters, nodes, namespaces, workloads, etc.  
    2. This ensures your CMDB reflects the real-time state of your Kubernetes environment.  


    Key Benefits  
    1. Real-time visibility into your containerized environment.  
    2. Automated population of CMDB with accurate and timely data.  
    3. Seamless integration between Kubernetes and ServiceNow using existing platform features like the ECC Queue and Table API. 

 

 

 

Have a question? Just drop us a note!

Latest Articles

Kaptius Hits 9 ServiceNow Validated Practice Accolades
ITSM   |   Sep 30, 2026

Kaptius Hits 9 ServiceNow Validated Practice Accolades

Kaptius adds FSM, Now Assist for CSM, Now Assist for ITSM and Manufa...

From Service Portal to Employee Slate: How ServiceNow Otto Is Rewriting the Employee Experience
now-assist   |   Sep 08, 2026

From Service Portal to Employee Slate: How ServiceNow Otto Is Rewriting the Employee Experience

ServiceNow Otto powers Employee Slate's AI-first experience, replaci...

The EU AI Act timetable after the Digital Omnibus: what actually applies, and when
AI   |   Aug 04, 2026

The EU AI Act timetable after the Digital Omnibus: what actually applies, and when

The Digital Omnibus deferred the EU AI Act’s high-risk obligations t...