0
3.14.1
Australia, Zurich, Yokohama, Xanadu
Standalone Application
The Kubernetes Visibility Agent offers cutting-edge monitoring for Kubernetes resources, performing continuous discovery and promptly reporting changes. It keeps your Configuration Management Database (CMDB) up to date with the latest data for optimal accuracy. Upon deployment, the KVA sets up a Deployment resource in your cluster, featuring an Informer pod. This pod connects to the Kubernetes API server, efficiently receiving and processing resource events.
Achieve unparalleled visibility into your on-premises Kubernetes clusters and cloud deployments, including Amazon EKS, Google GKE, Azure AKS, Red Hat OpenShift, and Rancher. Enhance your resource management and operational efficiency with the Kubernetes Visibility Agent.
- The component reports continuously to the ServiceNow instance and populates the CMDB with Kubernetes resources in near real-time.
- Tested with multiple Kubernetes platforms: EKS, AKS, GKE, OKE, Openshift, and on-prem.
Informer Version 2.5.0 - [March 2026 Store Release]
New
- Service maps now include Kubernetes and all related service resources beyond the Kubernetes environment.
- Kubernetes Service Maps offer more control over the CI visualization.
- KubeVirt VMs running in Kubernetes are being now added to the CMDB.
- Service mapping with KVA for micro-services is supported.
- KVA pod can run in an OKE (Oracle Kubernetes Engine) environment.
Fixed
- KVA now populates ObjectID in alignment with SGC for EKS, AKS and GKE cluster environments.
Licensing requirements: Customers need to have ITOM Visibility Subscription for this feature.
Notes:
To get the full new functionality of "Kubernetes Visibility Agent", first upgrade Kubernetes Visibility Agent and then upgrade the informers running in Kubernetes clusters, either using "helm upgrade..." command or by applying the latest k8s_informer.yaml.
Other Requirements:
Limitations and known issues:
- File based discovery probe is not supported with ACC.
Special Notes:
To get the full new functionality of "CNO for Visibility", first upgrade Agent Client Collector for Visibility and then upgrade the informers running in Kubernetes clusters, either using "helm upgrade..." command or by applying the latest k8s_informer.yaml.
- IPv6 Support:
- The agent can run on dual-stack (IPv4 + IPv6) or on IPv6 only systems.
- Datapoints supporting IPv6:
- CI (computer, server) ip_address
- Network Adapters: ip_address and netmask (prefix format for IPv6, i.e. 64)
- CI IPs: IP address, IP version and netmask
- TCP Connections: IP
- Use sn_agent.ci_prefers_ip_version to force IPv4 or IPv6 address for single attributes on dual-stack environments.
- If you manually added a custom Discovery Source, you may need to add the AgentClientCollector (and ACC-Visibility) sources manually.
- CI Name coming from computername vs. DNS hostname on Windows, now using the following properties:
- glide.discovery.hostname.wmi_trusted
- glide.discovery.hostname.case
- Ability to choose the type of required serial number [BIOS, Baseboard and others] to the computer CI serial_number attribute via the sys property sn_agent.ci_serial_number.pref_order.
- OS users: the sys_property sn_acc_visibility.persist_os_user_type controls what the local_user script will collect. By default, it collects the local users and the special/system accounts. When running on a Windows Domain Controller, the data collection is skipped for OS users.
- Network Adapters and CI IPs: to exclude some records from being stored in the CMDB, use the following property: sn_acc_visibility.network_adapter_exclusion_list. This is helpful for devices running in a home or other remote network during the time of discovery.
- The deletion strategy for DNS name matches the default behavior for Discovery.
- Enable MultiSource CMDB with Reconciliation rules if it conflicts with other data sources, for example if the agent blanks an attribute coming from another source.
- To enable the last access time for SAM - Software Usage, Read access has to be granted in the UserAssist entry in the registry, as per our official documentation. Either run the agent service as Local SYSTEM account, or enable an ACL on UserAssist for each User SID. Do *not* attempt to apply that ACL from the top HKEY_USERS, as it would induce severe side effects on the user's environment.
- To enable Total Usage metrics for SAM, see the KB article in the Supporting Links section.