Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

CheckerInventoryConfig

Since MOSK 25.2 and management 2.30.0

This section describes the CheckerInventoryConfig custom resource (CR) used in the network connectivity monitoring API on a target cluster. The CheckerInventoryConfig object is automatically created and managed by netchecker-controller on the target cluster in the netchecker namespace. The name of the object is hardcoded to mcc-netchecker-inventory-config.

Warning

Do not manually create or delete the CheckerInventoryConfig object to prevent overwriting by netchecker-controller. You can only reconfigure the existing object if you enable manual configuration as described in Manual configuration of network infrastructure monitoring.

The purpose of the CheckerInventoryConfig object is to include information about cluster nodes and that subnets are present on these nodes. The object status provides information about IP addresses related to each subnet detected on the node including error messages, if any. For more details, see Infrastructure connectivity monitoring.

For demonstration purposes, the CheckerInventoryConfig CR is split into the following sections:

CheckerInventoryConfig metadata

The CheckerInventoryConfig CR metadata contains the following fields:

  • apiVersion

    API version of the object that is cnnc.mirantis.com/v1alpha1.

  • kind

    Object type that is CheckerInventoryConfig.

  • metadata

    Object metadata that contains the following subfields:

    • name

      Object name.

    • namespace

      Project in which the CheckerInventoryConfig object is created.

Metadata example:

apiVersion: cnnc.mirantis.com/v1alpha1
kind: CheckerInventoryConfig
metadata:
  name: cic-sample
  namespace: default

CheckerInventoryConfig spec

The spec object field contains configuration for a CheckerInventoryConfig object and has the following fields:

  • subnetsConfig

    List of subnets with their ranges that are part of network connectivity monitoring. Contains the following fields:

    • name

      Subnet name or namespaced name.

    • tag

      Optional subnet tag to be set by the operator. By default, equals to the subnet name.

    • range

      List of subnet ranges.

  • nodesConfig

    List of nodes with expected subnets containing IP addresses to be present on each node. Contains the following fields:

    • nodeName

      Name of the node.

    • nodeSelector

      Selector for the cluster nodes.

    • expectedSubnetTags

      List of subnets containing IP addresses to be present on the node.

CheckerInventoryConfig configuration example:

spec:
  nodesConfig:
  - expectedSubnetTags:
    - default/k8s-lcm-nics
    - default/k8s-pxe-nics
    nodeName: master-0
  - expectedSubnetTags:
    - default/k8s-lcm-nics
    - default/k8s-pxe-nics
    nodeName: master-1
  - expectedSubnetTags:
    - default/k8s-lcm-nics
    - default/k8s-pxe-nics
    nodeName: master-2
  subnetsConfig:
  - name: default/k8s-lcm-nics
    ranges:
    - 192.168.9.101-192.168.9.120
    tag: default/k8s-lcm-nics
  - name: default/k8s-pxe-nics
    ranges:
    - 10.0.1.41-10.0.1.50
    tag: default/k8s-pxe-nics

CheckerInventoryConfig status

The status field of the CheckerInventoryConfig object contains the current state of the object:

  • nodes

    List of statuses per node. Contains the following fields:

    • name

      Node name.

    • foundBy

      Indicator of the node discovery: by name or by node selector.

    • IPAddresses

      List of per-subnet data found on the node. Contains the following fields:

      • subnetTag

        Tag or name of the subnet.

      • IPAddress

        IP address detected on the node for the related subnet.

      • interface

        Interface name where the IP address is detected.

      • mtu

        MTU size configured on the interface.

    • error

      Error message in case the IP address is not detected on the node. Otherwise, this field is omitted.

    • updatedAt

      Internal. Last time when status for the defined node has been updated to ensure that Netchecker inventory agents are functional.

  • error

    Summary of per-node errors.

  • overallStatus

    Summary of per-node statuses.

CheckerInventoryConfig status example:

status:
  nodes:
  - foundBy: name
    ipAddresses:
    - interface: k8s-lcm
      ipAddress: 192.168.9.102/24
      mtu: 9050
      subnetTag: default/k8s-lcm-nics
    - interface: k8s-pxe
      ipAddress: 10.0.1.42/24
      mtu: 9050
      subnetTag: default/k8s-pxe-nics
    name: master-0
    status: ok
    updatedAt: "2025-07-18T14:48:19Z"
  - foundBy: name
    ipAddresses:
    - interface: k8s-lcm
      ipAddress: 192.168.9.101/24
      mtu: 9050
      subnetTag: default/k8s-lcm-nics
    - interface: k8s-pxe
      ipAddress: 10.0.1.41/24
      mtu: 9050
      subnetTag: default/k8s-pxe-nics
    name: master-1
    status: ok
    updatedAt: "2025-07-18T14:48:19Z"
  - foundBy: name
    ipAddresses:
    - interface: k8s-lcm
      ipAddress: 192.168.9.103/24
      mtu: 9050
      subnetTag: default/k8s-lcm-nics
    - interface: k8s-pxe
      ipAddress: 10.0.1.43/24
      mtu: 9050
      subnetTag: default/k8s-pxe-nics
    name: master-2
    status: ok
    updatedAt: "2025-07-18T14:48:19Z"
  overallStatus: ok