Pulling additional resources from Kubernetes clusters into the CMDB

  • Release version: Yokohama
  • Updated January 30, 2025
  • 1 minute to read

    • You can configure the Kubernetes Visibility Agent Informer to pull extra resources from Kubernetes clusters into the Configuration Management Database (CMDB), in addition to the resources it sends to the database by default. By pulling in additional resources beyond the default set, you can enhance visibility into your Kubernetes clusters.

    The Informer collects data on Kubernetes resources, sends the collected data to the instance, and updates the appropriate tables in the CMDB. For a list of the resources the Informer pulls into the CMDB by default, see Data collected by CNO for Visibility.

    For every additional Kubernetes resource you want the Informer to pull into the CMDB, the system creates a Configuration Item (CI) in the cmdb_ci_kubernetes_component target table. Alternatively, extra resources can be pulled to custom tables that extend the cmdb_ci_kubernetes_component table. For example, you could create a u_cmdb_ci_kubernetes_configmap table for all ConfigMap resources in the cluster. The system creates a relation and a reference from the table to the cluster CI for every additional resource. If the resource is namespaced, a relation to the namespace CI is created.

    By default, the Informer pulls the following information from the Kubernetes cluster for each additional resource:
    • Name
    • Namespace (for namespaced resources)
    • Kubernetes ID
    • API version
    • Kind
    • Labels and Annotations

    Along with this default data, you can make the Informer pull further information on the additional resources into the CMDB. By default, the system stores this extra data in the attributes field of the cmdb_ci_kubernetes_component table. You can also create a custom field per additional resource for storing the extra information.

    Kubernetes Visibility Agent enables you to filter additional resources by defining filtering conditions. If a condition shows a match, the Informer sends the resource to the CMDB.

    For more detailed information and procedures for pulling additional resources from Kubernetes clusters into the CMDB, see the Discovering additional Kubernetes resources using CNO for Visibility (Informer) [KB1638668] article in the Now Support Knowledge Base.