#Workloads

The workload pages in this section cover project-scoped runtime resources used to run application code, finite tasks, and scheduled tasks.

Use these pages when you need to create, inspect, update, troubleshoot, or remove workloads in a selected project, cluster, and namespace context.

Some workload types can also be reached from other console views, but this section is organized around workload intent so you can choose the right operational path more quickly.

#Long-running application workloads

Use these pages for workloads that stay running and represent the main runtime units of an application:

When you manage these workloads from the Applications view, treat the selected cluster and namespace as fixed runtime scope. Update operations change the workload definition inside the current scope, but they do not move the workload to a different cluster or namespace.

• Deployments
• StatefulSets
• DaemonSets
• Pods

#Scheduled or finite execution workloads

Use these pages for workloads that stop after completion or run on a schedule:

• CronJobs
• Jobs

#Choose the right workload page

In most cases:

• Start with Deployments for common stateless application workloads.
• Use StatefulSets when stable identity, ordered rollout, or per-replica storage matters.
• Use DaemonSets when the workload should run broadly on matching nodes.
• Use CronJobs or Jobs when the main question is scheduled or finite execution.
• Use Pods when you need to inspect the actual runtime instances behind higher-level workloads.