Workloads
Kuboard covers every built-in Kubernetes workload type — Deployment, StatefulSet, DaemonSet, Job, CronJob and Pod — along with HPA (Horizontal Pod Autoscaling) and Continuous Deployment (CD).
Quick Navigation
| Section | Content | When to Read |
|---|---|---|
| Deployment | Replica sets with rolling updates and rollbacks | Stateless services and web apps |
| StatefulSet | Stateful replicas with stable network identity and storage | Databases, message queues and other stateful workloads |
| DaemonSet | One Pod per Node (or matching Node selector) | Node-level agents such as log shippers and CNI plugins |
| Job / CronJob | One-shot and scheduled batch workloads | Data processing, cleanup and scheduled tasks |
| Pod | Lowest-level Pod view, container state, terminal and logs | Debugging individual containers and accessing shell |
| HPA | Horizontal Pod Autoscaling on CPU, memory or custom metrics | Scale replicas based on load |
| Continuous Deployment (CD) | Image tag update and rolling restart APIs | Drive releases from CI pipelines or AI agents |
Recommended Reading Order
- First deployment — open Deployment and ship a stateless application;
- Stateful workloads — move to StatefulSet once the application needs stable identity or persistent storage;
- Node-level workloads — read DaemonSet for cluster-wide agents;
- Batch jobs — read Job / CronJob for one-off or scheduled tasks;
- Autoscaling — configure HPA to handle variable load;
- Release automation — integrate CI with Continuous Deployment (CD) to replace manual restarts.
Where to go next
After you have a workload running, configure its ConfigMap / Secret and PVC bindings. Use the Operations section's Events and Resource Map to keep an eye on the workload in production.