Workloads

Manage all Kubernetes workload types: StatefulSets, DaemonSets, Jobs, CronJobs, and ReplicaSets.

Workload Types

StatefulSets

Manage stateful applications with ordered pod creation and stable network identities.

StatefulSet Features

Viewing StatefulSets

StatefulSet Details

• Pod list showing ordered names (pod-0, pod-1, pod-2)
• PVC bindings per pod
• Service association
• Update strategy (RollingUpdate or OnDelete)

Scaling StatefulSets

1. Open StatefulSet detail
2. Adjust replica count
3. Click "Scale"
4. Pods added/removed in reverse order

Scaling Behavior:

• Scale up: Creates pod-N, waits for Ready, creates pod-N+1
• Scale down: Deletes pod-N, waits for termination, deletes pod-N-1

Restarting StatefulSets

Perform rolling restart:

1. Click "Restart"
2. Pods restart in reverse order (highest to lowest)
3. Each pod must be Ready before next restarts

DaemonSets

Run exactly one pod on every node (or subset of nodes with selectors).

DaemonSet Features

Viewing DaemonSets

DaemonSet Details

• Pod distribution across nodes
• Node selector rules
• Update strategy (RollingUpdate or OnDelete)
• Tolerations configured

Common DaemonSet Uses

Restarting DaemonSets

Rolling restart across all nodes:

1. Click "Restart"
2. Pods restart node-by-node
3. Max unavailable controls rollout speed

Jobs

Run pods to completion for batch processing tasks.

Job Features

Viewing Jobs

Job Details

• Pod list (completed and failed pods)
• Completion status
• Active pods
• Failed pod count
• Conditions (Complete, Failed)

Job Status

Deleting Jobs

1. Click "Delete" on job
2. Confirm deletion
3. Job and all pods removed

Note: Completed job pods remain until job is deleted (for log inspection).

CronJobs

Schedule recurring jobs using cron syntax.

CronJob Features

Viewing CronJobs

CronJob Details

• Schedule and next run time
• Job history (last 5 runs)
• Active jobs
• Concurrency policy
• Suspend status

Triggering CronJobs Manually

Run job immediately without waiting for schedule:

1. Click "Trigger Now"
2. New job created with timestamp suffix
3. Job runs like scheduled execution

Suspending CronJobs

Pause scheduling temporarily:

1. Click "Suspend"
2. No new jobs created
3. Active jobs continue running
4. Click "Resume" to restart scheduling

Common CronJob Schedules

ReplicaSets

Manage identical pod replicas (usually controlled by Deployments).

ReplicaSet Features

Viewing ReplicaSets

When to Use

Deployments create ReplicaSets automatically - you rarely manage ReplicaSets directly.

Direct ReplicaSet use cases:

• Custom controllers
• Advanced deployment strategies
• Legacy applications migrating from ReplicationControllers

Scaling ReplicaSets

1. Open ReplicaSet detail
2. Adjust replica count
3. Click "Scale"

Warning: If owned by Deployment, Deployment will override this change.

Example: Managing a StatefulSet

StatefulSet Overview

StatefulSet: postgresql
Namespace:   production
Replicas:    3/3
Strategy:    RollingUpdate

Pod List

Scaling from 3 to 5

Scale-Up Process:

10:30:00  Scaling postgresql from 3 to 5 replicas
10:30:01  Creating pod postgresql-3
10:30:02  Creating PVC data-postgresql-3
10:30:15  Pod postgresql-3 Running and Ready
10:30:16  Creating pod postgresql-4
10:30:17  Creating PVC data-postgresql-4
10:30:30  Pod postgresql-4 Running and Ready
10:30:30  StatefulSet successfully scaled to 5 replicas

After Scaling

StatefulSet: postgresql
Namespace:   production
Replicas:    5/5
Pods:        postgresql-0 (Running)
             postgresql-1 (Running)
             postgresql-2 (Running)
             postgresql-3 (Running)
             postgresql-4 (Running)

Example: DaemonSet Monitoring

DaemonSet Overview

DaemonSet: node-exporter
Namespace: monitoring
Nodes:     12
Desired:   12
Current:   12
Ready:     12

Node Distribution

Rolling Restart

Restart Process:

10:45:00  Restarting DaemonSet node-exporter
10:45:01  Terminating pod on node-1
10:45:15  New pod on node-1 Running and Ready
10:45:16  Terminating pod on node-2
10:45:30  New pod on node-2 Running and Ready
...
10:50:00  All 12 pods restarted successfully

Example: CronJob Backup

CronJob Configuration

CronJob:     database-backup
Namespace:   production
Schedule:    0 2 * * *  (Daily at 2:00 AM)
Suspend:     False
Concurrency: Forbid

Job History

Manual Trigger

Trigger backup immediately for testing:

1. Click "Trigger Now" on database-backup
2. New job created: database-backup-manual-20240115-103000
3. Job runs with same configuration as scheduled execution

Result:

Job: database-backup-manual-20240115-103000
Status: Running
Active Pods: 1
Duration: 5m 30s

Troubleshooting