Managing Infrastructure Linkages for Kubernetes Clusters

If Commander is also managing the cloud infrastructure where the cluster resides, Commander automatically links Kubernetes nodes to the underlying VMs.

Note: For Commander to manage the cloud infrastructure where the cluster resides, the vCenter, AWS, Azure or GCP cloud must be added to Commander as a cloud account. For more information, see Cloud Account Management.

In this topic:

Viewing infrastructure linkages for Kubernetes clusters

Access through:

Views > Inventory > Infrastructure or Applications

Available to:

Any level of access rights on both Kubernetes cluster and underlying cloud account

To view infrastructure linkages for a Kubernetes cluster:

  1. From the Inventory tree, select a Kubernetes cloud account.
  2. Click the Linkages tab.
  3. A list of Kubernetes resources is displayed. If a resource is linked to the underlying infrastructure, link details appear in the Infrastructure section.

    Kubernetes links to underlying infrastructure

    If the resource isn't linked to the underlying infrastructure but a potential link has been found, a warning icon appears in the Resources list, and the potential link is displayed in the Infrastructure section.

    Kubernetes resource with suggested link

    Note: If you have permission, you can link the node to the underlying VM. See Manually linking Kubernetes nodes and underlying VMs.

    If the resource isn't linked to the underlying infrastructure and no potential link has been found, a warning icon appears in the Resources list and in the Infrastructure section.

    Kubernetes not linked to underlying infrastructure

    When there's no suggested linkage for a resource, this generally means that Commander isn't managing the underlying infrastructure, but it can also mean that Commander has not yet discovered a linkage.

    Note: If you have permission, you can manually run the linkage discovery task. See Manually running the linkage discovery task.

Removing linkages between Kubernetes nodes and VMs

If you determine that Commander has incorrectly linked a Kubernetes node, you can remove the link.

Access through:

Views > Inventory > Infrastructure or Applications

Available to:

Commander Role of Superuser, Enterprise Admin
Administrator access rights on Kubernetes cluster; some level of access rights on underlying VM

To correct a link between a node and its underlying VM:

  1. From the Inventory tree, select a Kubernetes node or its underlying VM.
  2. Click the Linkages tab.
  3. A blue hyperlink next to the Name property displays the linked VM or node name.

  4. Click Unlink.
  5. The link between the node and the VM is removed.

Manually running the linkage discovery task

Although Commander regularly discovers and updates linkages between Kubernetes nodes and underlying VMs, you can also manually run the task that discovers linkages.

Access through:

Views > Inventory > Infrastructure or Applications > Kubernetes cloud account

Available to:

Commander Role of Superuser, Enterprise Admin
Administrator access rights on Kubernetes cluster; some level of access rights on underlying VM

To manually run the task that discovers linkages between Kubernetes nodes and the underlying VMs:

  1. From the Inventory tree, select a Kubernetes cloud account.
  2. Click the Linkages tab.
  3. Click Run Discovery.
  4. Commander discovers and updates linkages between Kubernetes nodes and the underlying VMs.

  5. To see whether linkages were discovered or updated, double-click the Running Resource Linkage Discovery task in the Tasks area at the bottom of the Commander console.
  6. The Description column indicates the number of new links found.

  7. Click OK to close the dialog.

    Note: If you want to export the linkage discovery results as a CSV file, click Export.

Manually linking Kubernetes nodes and underlying VMs

Typically, Commander automatically establishes linkages between Kubernetes nodes and underlying VMs. However, if you run the linkage discovery task manually and Commander discovers a link, or if Commander discovers multiple potential linkages, you must complete the link between the node to the proper underlying VM.

Access through:

Views > Inventory > Infrastructure or Applications > Kubernetes cloud account

Available to:

Commander Role of Superuser, Enterprise Admin
Administrator access rights on Kubernetes cluster; some level of access rights on underlying VM

To complete links between Kubernetes nodes to underlying VMs:

  1. From the Inventory tree, select a Kubernetes cloud account.
  2. Click the Linkages tab.
  3. A list of Kubernetes resources is displayed.

    If a resource isn't linked to the underlying infrastructure, but one or more potential links have been found, a warning icon appears beside the resource in the Resources list, and the potential links to nodes are displayed in the Infrastructure section.

    Kubernetes resource with suggested link

  4. Select a node with a potential linkage.
  5. If the suggested link is valid, click Link.
  6. Click Yes to establish the link between the node and the VM.