Workloads
The Workloads section of the Kubernetes tab gives you visibility into every workload resource running on your cluster. Use the left sidebar to navigate between resource types: Pods, Deployments, StatefulSets, DaemonSets, Jobs, and CronJobs.
All views share a Namespace dropdown at the top of the page, which lets you filter results to a specific namespace. By default it is set to All Namespaces.
Pods
A Pod is the smallest deployable unit in Kubernetes. Each Pod represents one or more containers running together on a node. The Pods view lists every Pod across your cluster.
Pod Name
The name of the Pod. Click the copy icon alongside it to copy the name to your clipboard.
Namespace
The namespace the Pod belongs to.
Status
The current lifecycle phase of the Pod. A green dot indicates the Pod is running normally.
Node
The node the Pod has been scheduled and is running on.
Created
The date and time the Pod was created, including timezone.
Pod Status Values
Running
The Pod has been bound to a node and all containers have been started.
Pending
The Pod has been accepted by the cluster but is not yet running. It may be waiting for resources or for its container image to be pulled.
Succeeded
All containers in the Pod have completed successfully and will not be restarted.
Failed
One or more containers in the Pod terminated with an error.
Unknown
The state of the Pod could not be determined, usually due to a communication error with the node.
Deployments
A Deployment manages a set of identical, stateless Pods and ensures the desired number of replicas are running at all times. If a Pod fails, the Deployment controller automatically replaces it.
Name
The name of the Deployment. Click the copy icon alongside it to copy the name to your clipboard.
Namespace
The namespace the Deployment belongs to.
Ready
The number of replicas currently ready out of the total desired, displayed as ready/desired (e.g. 1/1).
Available
The number of replicas that are available to serve traffic.
Updated
The number of replicas that have been updated to the latest desired state.
Created
The date and time the Deployment was created, including timezone.
StatefulSets
A StatefulSet manages Pods that require stable identities and persistent storage, such as databases. Unlike Deployments, each Pod in a StatefulSet has a unique, stable network identity and storage that persists across restarts.
Name
The name of the StatefulSet. Click the copy icon alongside it to copy the name to your clipboard.
Namespace
The namespace the StatefulSet belongs to.
Ready
The number of replicas currently ready out of the total desired, displayed as ready/desired (e.g. 3/3). A value like 0/1 indicates replicas are desired but none are currently ready.
Current
The number of Pods that currently exist for this StatefulSet.
Updated
The number of Pods that have been updated to the latest version.
Created
The date and time the StatefulSet was created, including timezone.
DaemonSets
A DaemonSet ensures that a copy of a specific Pod runs on every node in the cluster (or a subset of nodes). DaemonSets are commonly used for cluster-wide services such as log collectors, monitoring agents, and GPU device plugins.
Name
The name of the DaemonSet. Click the copy icon alongside it to copy the name to your clipboard.
Namespace
The namespace the DaemonSet belongs to.
Desired
The number of nodes that should be running the DaemonSet Pod.
Current
The number of nodes that are currently running the DaemonSet Pod.
Ready
The number of nodes running the Pod in a Ready state.
Available
The number of nodes where the Pod is available and able to serve its intended function.
Created
The date and time the DaemonSet was created, including timezone.
Note: If the Ready or Available count is lower than Desired, it may indicate that some nodes are unable to run the Pod. This could be caused by resource constraints, node taints, or scheduling issues.
Jobs
A Job creates one or more Pods to carry out a specific task and tracks whether those Pods complete successfully. Once all Pods finish, the Job is considered complete. Jobs are commonly used for one-off tasks such as installing modules or running database migrations.
Job Name
The name of the Job. Click the copy icon alongside it to copy the name to your clipboard.
Job Status
The current status of the Job. A green dot alongside Complete indicates the Job finished successfully.
Namespace
The namespace the Job belongs to.
Kind
The resource kind associated with the Job, where applicable.
Created
The date and time the Job was created, including timezone.
CronJobs
A CronJob creates Jobs on a repeating schedule, similar to a cron task in Linux. CronJobs are useful for recurring automated tasks such as backups, report generation, or cleanup operations.
If no CronJobs have been configured on your cluster, the view will display No Results Found. This is expected for clusters that do not have any scheduled recurring workloads defined.
Last updated