Open navigation

Kubernetes Workloads

The Workloads page manages applications running in a cluster, covering six resource types: Pods, Deployments, StatefulSets, DaemonSets, Jobs, and CronJobs. All list pages support namespace filtering and name search.

Kubernetes Workloads

The Workloads page manages applications running in a cluster, covering six resource types: Pods, Deployments, StatefulSets, DaemonSets, Jobs, and CronJobs. All list pages support namespace filtering and name search.

Pods

Pod list page

The list page displays all Pods in a table:

FieldDescription
NamePod name; click to open the detail page
NamespaceThe namespace the Pod belongs to
StatusCurrent Pod status (Running, Pending, Failed, etc.)
ReadyReady containers / Total containers
IPPod IP address
RestartsContainer restart count
NodeNode the Pod is running on
PortsExposed container ports
AgeResource creation time

List page actions: Create Pod, Edit Pod, Delete Pod.

Direct Pod creation is typically for debugging or short-lived tasks. For production workloads, use controllers such as Deployments or StatefulSets.

Click a Pod name to open the detail page with the following tabs:

Overview — Displayed as cards showing basic info (Phase, Pod IP, Host IP, Node, Restarts, QoS Class, UID, Created At), conditions, labels, annotations, related services (auto-matched by Pod labels), and events.

Logs — View real-time logs from containers within the Pod. Logs may be empty if the container hasn't started or has exited.

The Ready column shows "ready containers / total containers". If the count is less than total, some containers have not passed readiness probes.

Deployments

Deployment list page

The list page displays all Deployments in a table:

FieldDescription
NameDeployment name; click to open the detail page
NamespaceThe namespace the Deployment belongs to
ReadyReady replicas / Desired replicas
Up-to-dateReplicas updated to the latest template
AvailableAvailable replicas
AgeResource creation time

List page actions: Create Deployment, Scale, Restart, Delete.

Deployment detail page

Click a name to open the detail page with top action buttons: Restart (rolling restart), Scale, Edit, Delete. The detail page has the following tabs:

Overview — Displayed as cards showing basic info, conditions, selector, labels, annotations, and events.

Pods — All Pods managed by this Deployment, with columns for name, namespace, status, ready, restarts, node, and IP.

Restarting a Deployment is a rolling restart, implemented by patching the Pod template rather than deleting and recreating. Scaling to 0 stops all Pods for this Deployment.

Create Deployment form

Creating a Deployment supports both form mode and YAML mode. The form mode includes Pod template configuration: container configuration (image, ports, environment variables, resource requests and limits), volumes, security context, tolerations, and probes (liveness, readiness, startup).

StatefulSets

StatefulSet list page

The list page displays all StatefulSets in a table:

FieldDescription
NameStatefulSet name
NamespaceThe namespace the StatefulSet belongs to
Service NameAssociated Headless Service name
ReadyReady replicas / Desired replicas
Current ReplicasCurrent actual replica count
AgeResource creation time

List page actions: Create StatefulSet, Scale, Restart, Delete.

Click a name to open the detail page with top action buttons: Restart, Scale, Edit, Delete. The detail page has the following tabs:

Overview — Basic info, status, selector, labels, annotations, and events.

Pods — All Pods managed by this StatefulSet.

PVCs — PersistentVolumeClaims created by this StatefulSet, showing name, storage class, access modes, and storage request.

Scaling down a StatefulSet removes the highest-numbered Pod only; corresponding PVCs are not deleted. Deleting a StatefulSet does not automatically delete associated PVCs — manual cleanup is required.

DaemonSets

DaemonSet list page

The list page displays all DaemonSets in a table:

FieldDescription
NameDaemonSet name
NamespaceThe namespace the DaemonSet belongs to
DesiredDesired number of Pods to schedule
CurrentCurrently running Pod count
ReadyReady Pod count
AgeResource creation time

List page actions: Create DaemonSet, Restart, Delete.

Click a name to open the detail page with top action buttons: Restart, Edit, Delete. The detail page has the following tabs:

Overview — Basic info, conditions, selector, labels, annotations, and events.

Pods — All Pods managed by this DaemonSet.

A DaemonSet runs one Pod on every eligible node. New nodes automatically get a Pod, so there is no manual scale operation.

Jobs and CronJobs

Jobs and CronJobs share the same list page, switched via tabs.

Jobs list page

Jobs tab

FieldDescription
NameJob name
NamespaceThe namespace the Job belongs to
CompletionsCompleted / Desired count
DurationJob run duration
StatusCompletion status (Complete / Failed)
AgeResource creation time

List page actions: Create Job, Delete Job.

CronJobs tab

FieldDescription
NameCronJob name
NamespaceThe namespace the CronJob belongs to
ScheduleCron expression
SuspendedWhether the CronJob is suspended
ActiveCurrently active Job count
Last ScheduleTime of the last triggered schedule
AgeResource creation time

Job Detail

Click a Job name to open the detail page with top action buttons: Edit, Delete. The detail page has the following tabs:

Overview — Basic info, conditions, selector, labels, annotations, and events.

Pods — All Pods created by this Job.

Deleting a Job also deletes all Pods it created. For Failed Jobs, inspect the associated Pod logs to determine the cause.

CronJob Detail

Click a CronJob name to open the detail page with top action buttons: Trigger (manual trigger), Suspend / Resume, Edit, Delete. The detail page has the following tabs:

Overview — Basic info, Job template, labels, annotations, and events.

Jobs — All Jobs created by this CronJob, showing name, namespace, completions, status, and age.

Suspending a CronJob stops new Jobs from being triggered, but already created Jobs continue running. Manual trigger creates a new Job immediately, independent of the schedule. CronJobs use Cron expressions to define schedules — confirm the timezone is correct.

This document was updated on 2026-04-25 09:00