Workload Status¶
A workload is an application running on Kubernetes, and in Kubernetes, whether your application is composed of a single same component or composed of many different components, you can use a set of Pods to run it. Kubernetes provides five built-in workload resources to manage pods:
You can also expand workload resources by setting Custom Resource CRD. In the fifth-generation container management, it supports full lifecycle management of workloads such as creation, update, capacity expansion, monitoring, logging, deletion, and version management.
Pod Status¶
Pod is the smallest computing unit created and managed in Kubernetes, that is, a collection of containers. These containers share storage, networking, and management policies that control how the containers run. Pods are typically not created directly by users, but through workload resources. Pods follow a predefined lifecycle, starting at Pending phase, if at least one of the primary containers starts normally, it enters Running , and then enters the Succeeded or Failed stage depending on whether any container in the Pod ends in a failed status.
Workload Status¶
The fifth-generation container management module designs a built-in workload life cycle status set based on factors such as Pod status and number of replicas, so that users can more realistically perceive the running status of workloads. Because different workload types (such as Deployment and Jobs) have inconsistent management mechanisms for Pods, different workloads will have different lifecycle status during operation, as shown in the following table.
Deployment, StatefulSet, DamemonSet Status¶
| Status | Description |
|---|---|
| Waiting | 1. A workload is in this status while its creation is in progress. 2. After an upgrade or rollback action is triggered, the workload is in this status. 3. Trigger operations such as pausing/scaling, and the workload is in this status. |
| Running | This status occurs when all instances under the workload are running and the number of replicas matches the user-defined number. |
| Deleting | When a delete operation is performed, the payload is in this status until the delete is complete. |
| Exception | Unable to get the status of the workload for some reason. This usually occurs because communication with the pod's host has failed. |
| Not Ready | When the container is in an abnormal, pending status, this status is displayed when the workload cannot be started due to an unknown error |
Job Status¶
| Status | Description |
|---|---|
| Waiting | The workload is in this status while Job creation is in progress. |
| Executing | The Job is in progress and the workload is in this status. |
| Execution Complete | The Job execution is complete and the workload is in this status. |
| Deleting | A delete operation is triggered and the workload is in this status. |
| Exception | Pod status could not be obtained for some reason. This usually occurs because communication with the pod's host has failed. |
CronJob status¶
| Status | Description |
|---|---|
| Waiting | The CronJob is in this status when it is being created. |
| Started | After the CronJob is successfully created, the CronJob is in this status when it is running normally or when the paused task is started. |
| Stopped | The CronJob is in this status when the stop task operation is performed. |
| Deleting | The deletion operation is triggered, and the CronJob is in this status. |
When the workload is in an abnormal or unready status, you can move the mouse over the status value of the load, and the system will display more detailed error information through a prompt box. You can also view the log or events to obtain related running information of the workload.