Five Steps from Recommendation to Action
The automation engine continuously evaluates workloads and executes rightsizing safely, with no human in the loop required.
Pull Recommendations
Pulls ML-driven rightsizing recommendations from the Kubex platform via the Gateway API.
Evaluate Policy
Reconciler matches each workload against Proactive, Static, Rollback, GPU, and Pod Affinity policies; a referenced AutomationStrategy defines how automation executes.
Run Safety Checks
Multiple guardrails and filters protect every resize attempt, spanning HPA, ResourceQuota, LimitRange, node headroom, workload availability, readiness, and namespace guards.
Execute
Uses in-place container resize on supported Kubernetes 1.33+ clusters, with eviction-based fallback when in-place resize is unavailable and eviction is allowed.
Monitor & Rollback
Supports rollback monitoring and backoff when a matching rollback policy is configured, so unhealthy changes can be reverted.
Deploy in Minutes
Install via Helm, then define automation policies as Kubernetes CRDs. GitOps-ready from day one.
# Add the Kubex Helm repo
helm repo add kubex https://densify-dev.github.io/helm-charts
helm repo update
# Install CRDs first
helm install kubex-crds kubex/kubex-crds \
--namespace kubex --create-namespace
# Install the automation engine
helm install kubex-automation-engine kubex/kubex-automation-engine \
--namespace kubex \
--set global.kubexUrl="https://your-tenant.kubex.ai" \
--set global.kubexApiToken="<your-token>"
# Verify health
kubectl get globalconfiguration global-config -o yaml
kubectl get events -A --field-selector reason=PrecheckFailed
apiVersion: rightsizing.kubex.ai/v1alpha1
kind: ProactivePolicy
metadata:
name: team-a-proactive
namespace: team-a
spec:
scope:
labelSelector:
matchLabels:
app.kubernetes.io/part-of: storefront
workloadTypes:
- Deployment
- StatefulSet
automationStrategyRef:
name: team-a-balanced
safetyChecks:
maxAnalysisAgeDays: 3
apiVersion: rightsizing.kubex.ai/v1alpha1
kind: AutomationStrategy
metadata:
name: team-a-balanced
namespace: team-a
spec:
enablement:
cpu:
requests:
downsize: true
upsize: true
memory:
requests:
downsize: true
upsize: true
inPlaceResize:
enabled: true
containerRestart: false
podEviction:
enabled: true
retryPodDisruptionBudget: true
Eliminate over-provisioned CPU and memory, the most common source of wasted cluster spend.
Higher cluster density through tighter resource allocation: more workloads per node, fewer idle resources.
Remove manual rightsizing from engineering workflows, so teams focus on features, not spreadsheets.
Multiple safety checks and policy-driven rollback mean optimization never compromises availability.
Ready to automate
Kubernetes optimization?
Deploy the Kubex Automation Engine in minutes with a single Helm chart.
