Cluster Resources
This section covers Kubernetes resources that operate at the cluster or infrastructure layer. These objects rarely carry business traffic directly, but they define capacity, quota, scheduling and policy boundaries.
Quick Navigation
| Section | Content | When to Read |
|---|---|---|
| Node | Node listing, labels and taints, drain and evict | Node maintenance, scaling, upgrades |
| Namespace | Creating namespaces, attaching quotas, isolating authorization | Multi-team or multi-environment isolation |
| ResourceQuota / LimitRange | Namespace-level resource quota and default request / limit | Control resource usage |
| Scheduling / PDB / Lease / RuntimeClass | PriorityClass, PodDisruptionBudget, Lease, RuntimeClass | Scheduling policy and availability guarantees |
| Admission Webhook | Validating and Mutating Webhook configuration viewer | Troubleshoot admission control |
| FlowControl | flowcontrol.apiserver.k8s.io API group and priorities | Tune apiserver rate limiting |
| DRA (Dynamic Resource Allocation) | DRA resource templates and claims | GPUs and other heterogeneous accelerators |
Recommended Reading Order
- First-time organization — split the cluster by team or environment with Namespace, then set boundaries via ResourceQuota / LimitRange;
- Day-to-day operations — read Node for bring-up and tear-down; read the PDB section of Scheduling / PDB / Lease / RuntimeClass for rolling upgrades and self-healing;
- Platform team — read Admission Webhook and FlowControl;
- AI and heterogeneous resources — read DRA (Dynamic Resource Allocation).
Tier 1 resources
LimitRange, ResourceQuota, PriorityClass, PodDisruptionBudget, EndpointSlice and Lease are classified as Tier 1 resources. Kuboard does not cache them by default — they are fetched directly from the apiserver. Their form pages accept ?demo=true to preload sample data so you can verify the controls without a live cluster.