ScaleOps via GitOps
ScaleOps supports GitOps control for all optimization products through workload annotations, AutomatedNamespace (ANS) CRD configuration, and cluster ConfigMaps. This provides declarative control over automation and policy assignment across Workload Rightsizing, Replicas Optimization, Spot Optimization, and GPU Rightsizing.
Each product can be controlled independently using product-specific annotations and configuration fields.
Available Guides
Workload Actions
Learn how to control workload automation and policies using annotations:
- Automating workloads with product-specific annotations
- Setting workload policies for Rightsizing, Replicas, and Spot optimization
- Excluding workloads from automation
- Force override capabilities for automation and policies
Namespace Actions
Configure namespace-level automation and policies:
- Namespace annotations for workload rightsizing
- AutomatedNamespace CRD for multi-product optimization
- Custom namespace labels for selective automation
- Excluding namespaces from automation
Cluster Actions
Manage cluster-wide automation and policies:
- ConfigMap configuration for cluster operations
- Multi-product automation fields
- Default policy assignment across all optimization products
Action Precedence
Understand how different actions interact:
- Action hierarchy from highest to lowest precedence
- Exclude, Force, General, and Default action types
- Resetting workload control to default actions
- Script and GitOps reset methods
Policy
Create and configure optimization policies:
- Policy Custom Resources for rightsizing configuration
- Resource configuration for CPU and memory optimization
- Update policies for different workload types
- Stabilization windows and scaling thresholds
UI Integration
All GitOps actions (automation and policy assignment) can also be triggered from the ScaleOps UI. UI actions take precedence over GitOps configurations, ensuring that manual interventions can override automated settings when needed.
Event Log Attribution
Actions performed via GitOps (through workload annotations, AutomatedNamespace CRD, or cluster ConfigMaps) are recorded in the User Events log and attributed to the ANS user. This allows you to distinguish GitOps-driven changes from manual UI actions when auditing your event history.