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


---

# Kubernetes Visibility Agent support matrix

# Kubernetes Visibility Agent support matrix {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The Kubernetes Visibility Agent component is supported on several versions of Kubernetes and OpenShift and in various Kubernetes environments.
Note:  
To deploy KVA in the OKE (Oracle Kubernetes Engine) environment, you need to create a Kubernetes Cluster on Oracle Cloud Infrastructure. For more information, see the [Oracle](https://www.oracle.com/) documentation.

For the latest information, see the [Kubernetes Visibility Agent (formerly CNO for Visibility) Support Matrix \[KB1700730\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1700730) article in the Now Support Knowledge Base.

## FIPS-140 compliance {#cnov-support-matrix__section_fips_compliance}

FIPS-140 (Federal Information Processing Standard 140) is a US government standard for cryptographic modules used in regulated industries. In regulated markets that require FIPS-140 compliant code, the Kubernetes Visibility Agent Informer images have the following FIPS-140 compliance status:

* The main informer image is FIPS-140 compliant.
* The daemonset image used for traffic discovery is FIPS-140 compliant.
* The optional Syft scanner image used for container image scanning is not FIPS-140 compliant.
{#cnov-support-matrix__ul_fips_compliance}

## Windows nodes {#cnov-support-matrix__section_windows_nodes}

When the createServerCi parameter is set to <kbd class="ph userinput">true</kbd>, the Kubernetes Visibility Agent Informer creates a Windows Server \[cmdb_ci_win_server\] CI for each Windows Kubernetes node.
To configure server CIs for all
node types, see [Configure server CI creation for Kubernetes nodes](https://www.servicenow.com/docs/yK5Ct5WelQnYW9lKvOO8EA "Configure whether the Kubernetes Visibility Agent Informer creates a server CI for each Kubernetes node.").
* **[Kubernetes Visibility Agent (KVA) Performance Benchmark](https://www.servicenow.com/docs/zbDhrunTI9dUvpyuuszoTg)**   
  Performance tests help you estimate the load, memory, and CPU on the Instance and Kubernetes cluster.
* **[Discovering Kubevirt Virtual Machines](https://www.servicenow.com/docs/_aEDZ2ONrXBVyESHc8c2Iw)**   
  KubeVirt provides a unified development platform where developers can build, modify, and deploy applications in both Application Containers and Virtual Machines.
* **[Running Kubernetes Visibility Agent (KVA) at Scale](https://www.servicenow.com/docs/aeRB3lZf4BAMrOdgtnHSVQ)**   
  When you run Kubernetes Visibility Agent (KVA) (formerly CNO for Visibility) on more than 100 clusters, configure your system properties to help prevent loss of data from the informers.