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.

InfraConnectivityMonitor

Since MOSK 25.2 and management 2.30.0

This section describes the InfraConnectivityMonitor custom resource (CR) used in the management API. It contains all necessary information to enable network connectivity monitoring for the target cluster.

Note

This object must be created and managed on the management cluster.

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

InfraConnectivityMonitor metadata

The InfraConnectivityMonitor CR metadata contains the following fields:

  • apiVersion

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

  • kind

    Object type that is InfraConnectivityMonitor.

  • metadata

    Object metadata that contains the following subfields:

    • name

      Object name.

    • namespace

      Project in which the InfraConnectivityMonitor object is created.

Metadata example:

apiVersion: kaas.mirantis.com/v1alpha1
kind: InfraConnectivityMonitor
metadata:
  name: icm-sample
  namespace: default

InfraConnectivityMonitor spec

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

  • targetCluster

    Required. Name of the cluster on which network connectivity monitoring must be enabled. By default, connectivity monitoring is enabled for all cluster machines.

  • machineSelector

    Optional. A set of Machine objects to include for connectivity monitoring. Machines that do not match this selector will be excluded.

InfraConnectivityMonitor configuration example:

spec:
  machineSelector:
    matchLabels:
      label-name: "label-value"
  targetCluster: mosk-cluster

InfraConnectivityMonitor status

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

  • inventoryConfigStatus

    Status of the CheckerInventoryConfig object from the target cluster. For object description, see CheckerInventoryConfig. This status is periodically synced by the NetChecker controller.

    • nodes

      List of nodes with a detailed inventory status for each node. Contains the following fields:

      • error

        Description of the node issues, if any. Otherwise, the field is omitted.

      • machineName

        Name of the target machine.

      • nodeName

        Name of the corresponding Kubernetes node.

      • status

        Node status:

        • ok - node does not have any issues.

        • error - node has issues described in the error field. May also contain description of the reason why the node is excluded from connectivity monitoring.

    • statusMsg

      Overall status message of the CheckerInventoryConfig object.

  • targetsConfigStatus

    Status of the NetCheckerTargetsConfig object from the target cluster. For object description, see NetCheckerTargetsConfig. This status is periodically synced by netchecker-controller. Contains the following fields:

    • nodes

      List of nodes with detailed status of targets for each node. Contains the following fields:

      • error

        Description of the node issues, if any. Otherwise, the field is omitted.

      • machineName

        Name of the target machine.

      • nodeName

        Corresponding name of the Kubernetes node.

      • status

        Node status:

        • ok - node does not have any issues.

        • error - node has issues described in the error field.

      • targetsCount

        Amount of targets (nodes and subnets) for a particular node.

    • statusMsg

      Overall status message of the NetCheckerTargetsConfig object.

InfraConnectivityMonitor status example:

status:
  inventoryConfigStatus:
    nodes:
    - machineName: master-0
      nodeName: master-0
      status: ok
    - machineName: master-1
      nodeName: master-1
      status: ok
    - machineName: master-2
      nodeName: master-2
      status: ok
    statusMsg: ok
  targetsConfigStatus:
    nodes:
    - machineName: master-0
      nodeName: master-0
      status: ok
      targetsCount: "4"
    - machineName: master-1
      nodeName: master-1
      status: ok
      targetsCount: "4"
    - machineName: master-2
      nodeName: master-2
      status: ok
      targetsCount: "4"
    statusMsg: ok