Sign In
Sign In

The Dashboard tab displays charts for CPU load, memory usage, pod capacity, pod statuses, and container restarts. The charts are available for both master and worker nodes.

To download the configuration file for connecting to the cluster, click the download the configuration file link on the right.

De1f4ad4 3417 4be0 9472 3a4fc0511b22

CPU Core Load

  • Capacity: The total number of CPU cores on the node. Measured in cores or millicores.
  • Allocatable: The number of CPU cores available for scheduling applications on the node.
  • Resource Limit: The total CPU limit set for pods. This indicates the maximum CPU usage allowed for all pods on the node.
  • Resource Request: The total amount of CPU requested by all pods on the node.

9221ebf9 Ce3f 48c8 98ed 638a3c5bc5ab

Memory

  • Capacity: The total amount of memory on the node.
  • Allocatable: The amount of memory available for scheduling applications.
  • Resource Limit: The total memory usage limit set for all pods on the node.
  • Resource Request: The total amount of memory requested by all pods.

Ca744363 F224 48dc A22d 1ec7a5d4c1fe

Pods Capacity

  • Allocatable: The number of additional pods that can still be scheduled on the node.
  • Requested: The number of pods currently scheduled on the node.

F6a0ea6a 625d 4ac0 9f27 A62ba8743b85

Pods Status

  • Running: The pod has been successfully deployed and is running. All containers within the pod are up and running.
  • Failed: An error occurred during the execution of one or more containers in the pod. For example, a container exited with a non-zero status code or failed to access required resources.
  • Pending: The pod has not started yet because Kubernetes is still scheduling it to a node and has not yet allocated the necessary resources (e.g., node space, networking, or image pulling). To find out the reason, run the command:
kubectl describe node <node_name>
  • Unknown: Kubernetes cannot determine the current status of the pod, possibly due to lost connection with the node where the pod was running. This may indicate connectivity issues or system failures.
  • Succeeded: All containers in the pod have successfully completed their work. This status typically applies to pods that are designed for one-time execution (e.g., a Job).

94e6fc2a 33b5 45fb 986e 1a5d2e56f9fc

Was this page helpful?
Updated on 14 April 2026

Do you have questions,
comments, or concerns?

Our professionals are available to assist you at any moment,
whether you need help or are just unsure of where to start.
Email us
Hostman's Support