Skip to content

Benefits#

✅ Benefits of ClusterResourceSupervisor (Cluster-Scoped)#

  1. Centralized Control
  2. Enables cluster administrators to define global hibernation policies that apply across many namespaces or ArgoCD AppProjects.

  3. Ideal for cost optimization in large environments (e.g., dev/test clusters that sleep nights and weekends).

  4. Flexible Namespace Targeting

  5. Supports explicit namespace lists (names) and dynamic selection via label selectors (matchLabels, matchExpressions).

  6. Allows automatic inclusion of new namespaces that match certain labels (e.g., env: dev).

  7. ArgoCD Integration

  8. Can target ArgoCD AppProjects, enabling hibernation based on GitOps application boundaries.

  9. Useful in GitOps workflows where applications are grouped into projects—no need to track individual namespaces.

  10. Rich Observability & auditability

  11. Detailed status includes:
    • watchedNamespaces / ignoreNamespaces
    • sleepingNamespaces with per-application replica counts and kinds (Deployment/StatefulSet)

  12. Helps operators debug, verify, and report on hibernation impact.

  13. Cluster-Wide Efficiency

  14. One CR can manage dozens or hundreds of namespaces—reducing configuration sprawl.

✅ Benefits of ResourceSupervisor (Namespace-Scoped)#

  1. Self-Service for Teams
  2. Application owners or namespace tenants can define their own hibernation schedule without cluster-level permissions.

  3. Empowers autonomy while still enabling cost savings.

  4. Simplicity & Low Overhead

  5. Minimal spec: only requires a schedule (sleep/wake cron expressions).

  6. No need to understand label selectors, ArgoCD, or cross-namespace concerns.

  7. Namespace Isolation

  8. Each namespace can have independent schedules—e.g., staging sleeps weekends, QA sleeps every night.

  9. Avoids "one-size-fits-all" policies that may not suit all workloads.

  10. Lightweight Status

  11. Status tracks only currentStatus and nextReconcileTime—sufficient for local use cases.

  12. Reduces cognitive load and storage overhead.

  13. RBAC-Friendly

  14. Can be managed by users with only namespace-level roles (e.g., edit or custom roles), improving security posture.

🎯 When to Use Which?#

Need Solved By
Platform team managing 100 dev namespaces ClusterResourceSupervisor
Developer team wanting to hibernate their own namespace ResourceSupervisor
GitOps-driven environment using ArgoCD AppProjects ClusterResourceSupervisor
Avoiding privilege escalation for namespace owners ResourceSupervisor