Install Kubernetes Visibility Agent \(KVA\) Informer

task australia Updated Sep 10, 2026 6 min read cnov-deploy-install.md
Raw file servicenow.com

You can install Kubernetes Visibility Agent Informer using either a Helm chart or the Kubernetes YAML file provided by ServiceNow.

Before you begin

Role required: none

About this task

Kubernetes Visibility Agent supports Helm 4. Existing releases created with Helm 3 can be upgraded to Helm 4.

Procedure

  1. Install Kubernetes Visibility Agent Informer using one of the following options.

    • Install Kubernetes Visibility Agent Informer using a Helm chart.

      1. Edit the Helm install command.

        1. In the following command, replace NAMESPACE, INSTANCE_NAME, and CLUSTER_NAME with the relevant values and replace the HELM_URL with the URL of the most recent version, provided in the Kubernetes Visibility Agent (formerly CNO for Visibility) Helm Chart and Kubernetes YAML file releases [KB1564347] article in the Now Support Knowledge Base.

          Shell
          helm install -n NAMESPACE --set acceptEula=Y --set instance.name=INSTANCE_NAME --set clusterName="CLUSTER_NAME" {--set image.repository=COMPANY_REPO --set image.tag=COMPANY_TAG} {--set proxyUrl=http://proxy_host:proxy_port} k8s-informer HELM_URL

          Note:

          • The curly brackets indicate that the code segments they surround are optional. Use these code segments if the image must be pulled from your organization’s image repository or if outgoing traffic from your cluster flows through a proxy.

          • By passing --set acceptEula=Y, you agree to the End-User License Agreement. You can read the End-User License Agreement by extracting the EULA.pdf from informer-helm-<VERSION_NUMBER>.tgz.

          • If the Informer is installed in OpenShift, add the openShift parameter to the command and set it to true:

            Shell
            helm install -n NAMESPACE --set acceptEula=Y --set instance.name=INSTANCE_NAME --set clusterName="CLUSTER_NAME" {--set image.repository=COMPANY_REPO --set image.tag=COMPANY_TAG} {--set proxyUrl=http://proxy_host:proxy_port} **\{--set openShift=true\}** k8s-informer HELM_URL

            Note: If the Informer is not installed in OpenShift, there is no need to set this parameter.

          • If you use the Hybrid service maps to map resources both inside and outside the Kubernetes cluster, set the following parameters:

            Shell
            --set bringIngressAddresses=true --set bringNodeExternalIPs=true --set discoverK8sServiceExternalIps=true --set openShift=true

          • Upgrading Existing Kubernetes Visibility Agent Informer from Helm 3 to Helm 4: When Helm 4 is installed on your system and you want to migrate an existing Kubernetes Visibility Agent Informer from Helm 3 to Helm 4, use the Server-Side Apply flag:

            Shell
            helm upgrade k8s-informer <CHART_URL> --server-side=true [other flags] -n $NAMESPACE

            The --server-side=true flag explicitly migrates the Informer to Helm 4's Server-Side Apply model for improved conflict resolution.

        2. In the command, configure additional settings as needed:

      2. Run the command.

    • Install Kubernetes Visibility Agent Informer using the Kubernetes YAML file.

      1. Download the Kubernetes YAML ZIP file provided in the Kubernetes Visibility Agent (formerly CNO for Visibility) Helm Chart and Kubernetes YAML file releases [KB1564347] article in the Now Support Knowledge Base.

      2. Extract the k8s_informer.yaml and EULA.pdf files from the ZIP file.

      3. Edit the k8s_informer.yaml file.

        • Change the value of ACCEPT_EULA to "Y", as follows:

          Text
          - name: ACCEPT_EULA  value: "Y"

          Note: By changing the value to "Y", you agree to the End-User License Agreement included in the EULA.pdf file.

        • Replace all occurrences of <NAMESPACE> with the namespace in which you want to install the Informer.

        • Replace all occurrences of <INSTANCE_NAME> with the name of your instance, without the domain name.

        • Replace <CLUSTER_NAME> with the name of your cluster as it appears in the CMDB.

        • If the Informer is installed in OpenShift, change the value of the OPENSHIFT environment variable to true.

        • Enabling application service maps

      4. If you use the Hybrid service maps to map resources both inside and outside the Kubernetes cluster, set the following parameters:

        Text
        - name: BRING_INGRESS_ADDRESSES value: "true" - name: BRING_NODE_EXTERNAL_IPS value: "true" - name: DISCOVER_K8S_SERVICE_EXTERNAL_IP value: "true" - name: OPENSHIFT value: "true"

      5. Run the command:

        Shell
        kubectl apply -f k8s_informer.yaml

Result

Kubernetes Visibility Agent is deployed on the Kubernetes cluster and begins to stream data into your instance.

What to do next

For information about Kubernetes Visibility Agent administration and troubleshooting, see the Administrating and Troubleshooting Kubernetes Visibility Agent (formerly CNO for Visibility) [KB1532614] article in the Now Support Knowledge Base.

Parent Topic:Configuring Kubernetes Visibility Agent

Keywords Agent Client CollectorKubernetes Visibility Agent InformerInformerKubernetesVisibilityinstallationdeploymentCloud Native Operations for VisibilityCNO for Visibility
Search documentation
Search document titles and file paths on the australia branch