Kubernetes Workload Management

The Workloads group in the Cluster UI sidebar is where you browse and manage everything that runs application containers — Deployments, Pods, Jobs, and the other standard Kubernetes workload types.

Open the Workloads Section

1. Navigate to the Platform Console.
2. Click on your imported cluster to open its Cluster Overview page.
3. In the left sidebar, click Workloads to expand it.

Every list page in this group follows the same layout: a 🔍 search box, an All Namespaces filter dropdown, and a green + Create button top-right.

Deployments

A Deployment keeps a set number of identical app copies running and handles rolling updates — it’s the standard way to run and update a stateless app. Use this page when you need to check rollout status, scale an app up/down, or push a new image version.

Lists every Deployment with its Namespace, Pods (ready count), Images, and Age. Click a row to view or edit it; use + Create to deploy a new one.

Replica Sets

A Replica Set’s only job is to keep a fixed number of Pod copies alive. You rarely create these by hand — a Deployment creates and manages one for you behind the scenes. Check this page when troubleshooting why a Deployment isn’t scaling the way you expect.

Lists every Replica Set with its Namespace, Pods, Images, and Age.

Replication Controllers

The older, legacy way to keep a fixed number of Pod copies running — same idea as a Replica Set, kept for backward compatibility. New workloads should use Deployments instead; you’d only see entries here on older setups.

Lists every Replication Controller with its Namespace, Pods, Images, and Age. Click + Create ReplicationController to add one.

Stateful Sets

For apps where each Pod needs a stable identity and its own storage — databases, queues, anything that can’t just be swapped for an identical copy. Use this when running stateful services that care about pod order or persistent data.

Lists every Stateful Set with its Namespace, Pods, Images, and Age.

Daemon Sets

Runs one copy of a Pod on every node automatically — typically used for cluster-wide infrastructure like log collectors or monitoring agents that need to run everywhere. Check this page to confirm a node-wide agent has rolled out to all nodes.

Lists every Daemon Set with its Namespace, Pods, Dsired, Current-Scheduled, Up-to-date, Node Selector, Images, and Age — the Desired/Current/Up-to-date columns show rollout progress at a glance.

Jobs

A Job runs a task once until it completes — a backup, a migration script, a one-off batch process — then stops, unlike a Deployment which runs forever. Use this page to check whether a one-off task finished and how long it took.

Lists every Job with its Namespace, Annotations, Completions, Duration, Images, and Age.

Cron Jobs

A Cron Job runs a Job on a repeating schedule — like a nightly backup or a recurring cleanup task — so you don’t have to trigger it manually each time. Use the Suspend state here to pause a recurring task without deleting it.

Lists every Cron Job with its Namespace, Annotations, Schedule, Suspend, Active, Last Schedule, Images, and Age — the Schedule column shows the cron expression.

Pods

A Pod is the actual running container(s) — the smallest unit in Kubernetes. Every Deployment, StatefulSet, Job, etc. above ultimately creates Pods to do the real work. This is the page to check when you need to see real-time container health or debug a crash.

Lists every Pod with its Namespace, Ready, Status, Restarts, IP, Images, and Age — the only Workloads item with these extra live-state columns, useful for spotting crashing or restarting containers.

Quick Reference