This section describes how to view monitoring information on the cluster overview page.

For other information about the cluster overview page, please refer to View Cluster Overview Information.

Prerequisites

  • You need to join a cluster and have the Monitoring View permission in the cluster. For more information, see Cluster Members and Cluster Roles.

  • The WizTelemetry Monitoring extension must be installed and enabled on the KubeSphere platform.

Steps

  1. Log in to the KubeSphere web console with a user who has Monitoring View permissions and enter your cluster.

  2. Click Overview in the left navigation pane.

    The Overview page provides the following monitoring information:

    Area Description

    Cluster Quota Statistics

    CPU and memory quotas for containers and projects in the current cluster, including reserved amount, limit amount, and total amount.

    Node Resource Usage

    Total and real-time usage of CPU, memory, and disk for all nodes, as well as the total number of pods allowed to be created in the cluster and the number of pods already created. By default, each node allows a maximum of 110 pods.

    Click the corresponding area to view the real-time usage percentage of that resource.

    Pods

    The number of various types of pods in the current cluster.

    Pod status types include:

    • Pending: The pod has been accepted by the system, but at least one container has not been created or is not running. In this state, the pod may be waiting to be scheduled or waiting for the container image to be downloaded.

    • Running: The pod has been assigned to a node, all containers in the pod have been created, and at least one container is running, starting, or restarting.

    • Succeeded: All containers in the pod have terminated successfully (terminated with exit code 0) and will not be restarted.

    • Failed: All containers in the pod have terminated, and at least one container terminated with a non-zero exit code.

    • Unknown: The system is unable to retrieve the pod’s status. This state typically occurs due to communication failure between the system and the host where the pod is located.

    Pod QoS (Quality of Service) types include:

    • Guaranteed: Every container in the pod has memory limits, memory requests, CPU limits, and CPU requests set, and the memory limit equals the memory request, and the CPU limit equals the CPU request.

    • Burstable: At least one container in the pod does not meet the requirements for the Guaranteed type.

    • BestEffort: The containers in the pod are not configured with any memory limits, memory requests, CPU limits, or CPU requests.

    The QoS type of a pod determines its runtime priority. When system resources are insufficient to run all pods, the system prioritizes ensuring the operation of pods with a QoS type of Guaranteed, followed by pods with a QoS type of Burstable, and lastly, pods with a QoS type of BestEffort.

    Number of Pods Terminated and Restarted Due to OOM: The number of pods that were forcibly terminated and automatically restarted by the system due to insufficient memory (Out Of Memory).

    Number of Pending Pods: The number of pods that have been created but cannot start due to insufficient resources or scheduling issues.

    Number of Restarted Pods: The number of pods that have been automatically restarted due to failures or configuration changes.

    Kubernetes Status

    API requests per second, API request latency, pod scheduling count, and pod scheduling failure count for the current cluster.

    Resource Usage Ranking

    The top 5 nodes, pods, and projects with the highest usage of specific resources in the current cluster.

    • Select node, pod, or project from the left dropdown list, and choose different sorting criteria from the right dropdown list.

    • Click sort-ascending/sort-descending above the list to sort in ascending/descending order.

    • Click View More below to view detailed resource usage for nodes, pods, and projects.