Design a Kubernetes workload: choose the workload kind by statefulness, set the three probe types correctly, requests/limits with the resulting QoS class, HPA/VPA on a load-tracking signal, and a PodDisruptionBudget.
Scanned 9/23/2026
Skills Directorynpx -y skills add mcorbett51090/RavenClaude --skill k8s-workload-design --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of K8s Workload Design?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-k8s-workload-design)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: k8s-workload-design
description: "Design a Kubernetes workload: choose the workload kind by statefulness, set the three probe types correctly, requests/limits with the resulting QoS class, HPA/VPA on a load-tracking signal, and a PodDisruptionBudget."
---
# Kubernetes Workload Design
## Workload kind
| Need | Kind |
|---|---|
| Stateless web/API | **Deployment** |
| Stable identity/storage | **StatefulSet** |
| One per node | **DaemonSet** |
| Run to completion | **Job / CronJob** |
## Probes
- **liveness**: restart if hung
- **readiness**: gate traffic
- **startup**: protect slow boot
## Resources
Requests **schedule**, limits **cap**. Set both -> know your QoS (Guaranteed/Burstable/BestEffort).
## Scale & disruption
HPA on a load-tracking signal (often custom/external, not bare CPU) + a **PodDisruptionBudget** + graceful shutdown (preStop + grace).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
