Managing Clusters

Kommander allows you to monitor and manage very large numbers of clusters. Use the features described in this area to connect existing clusters, or to create new clusters whose lifecycle is managed by Konvoy. You can view clusters from the Clusters tab in the navigation pane on the left. You can see the details for a cluster by selecting the View Details link at the bottom of the cluster card or the cluster name in either the card or the table view.

Types

There are several types of clusters that display in the Clusters tab. The cluster type appears in the cluster card just under the cluster name.

Figure 1. A cluster card with its type highlighted

The type values include:

• Attached: An Attached cluster is one that was not created with Kommander. You cannot manage an Attached cluster’s lifecycle, but you can monitor it.
• Managed: A Managed cluster is a Konvoy cluster that was created with Kommander. You can use Kommander to manage a Managed cluster’s lifecycle.
• Management: This is the Konvoy cluster that hosts Kommander.

Statuses

A cluster card’s status line displays both the current status and the version of Kubernetes running in the cluster.

Figure 2. A cluster card with its status highlighted

The status list includes these values:

* These statuses only appear on Managed clusters.

Resources

The Resources graphs on a cluster card show you a cluster’s resource requests, limits, and usage. This allows a quick, visual scan of cluster health. Hover over each resource to get specific details for that specific cluster resource.

Figure 3. A cluster card with resources highlighted

For more detailed information, see the Kubernetes documentation about resources.

Platform services

Platform services, formerly called Addons, are services that the management cluster installs. You can visit a cluster’s detail page to see which platform services are enabled under the “Platform Services” section.

Figure 4. Cluster detail page

Review the workspace platform service resource requirements to ensure that the attached clusters have sufficient resources. For more information on platform services and how to customize them, see workspace platform services.

Custom service cards

Custom service cards can be added to the cluster detail page’s Platform Services section by creating a ConfigMap on the cluster. The ConfigMap must have a d2iq.io/addon label and must contain both name and dashboardLink data keys to be displayed. Upon creation of the ConfigMap, the Kommander UI will display a card corresponding to the data provided in the ConfigMap. Custom service cards have a Kubernetes icon and can link to a service running in the cluster, or use an absolute URL to link to any accessible URL.

ConfigMap example

apiVersion: v1
kind: ConfigMap
metadata:
  name: "my-service"
  namespace: "kommander"
  labels:
    "d2iq.io/addon": "my-service"
data:
  name: "My Service"
  dashboardLink: "/path/to/service"

Use a command similar to this one to create a new custom service ConfigMap:

$ cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: ConfigMap
metadata:
  name: "my-service"
  namespace: "kommander"
  labels:
    "d2iq.io/addon": "my-service"
data:
  name: "My Service"
  dashboardLink: "/path/to/service"
EOF