Getting Started
Use this page for the first hosted EcoScale workflow: connect a cluster, confirm that workloads have recommendations, and review one low-risk change.
What You’ll Need
Section titled “What You’ll Need”Before you begin, confirm that you have:
- An EcoScale account with access to
Settings->Clusters. - Kubernetes access to install the EcoScale agent Helm chart.
- Metrics for the workloads you want to evaluate.
- Access to view recommendations in EcoScale.
Install the agent with mode=readonly first. Use mode=apply only when the team is ready for EcoScale to patch target workloads. For installation options, RBAC, and secret handling, see Agent Helm Chart.
Before You Start
Section titled “Before You Start”EcoScale needs cluster, workload, and metrics data before it can produce useful recommendations. If you want cost impact estimates, configure CPU and memory pricing before prioritizing work by projected savings.
For cluster setup, see Clusters. For recommendation fields and review criteria, see Recommendations.
First Successful Workflow
Section titled “First Successful Workflow”Start with a cluster or namespace your team understands well.
- Confirm that the cluster appears in EcoScale.
- Open the workload inventory and select a workload with populated CPU or memory recommendations.
- Compare current requests and limits with the recommended values.
- Confirm the workload, namespace, cluster, and container names before taking action.
- If the recommendation is clear, apply it manually during an appropriate change window and validate the result.
A successful first rollout proves that the cluster is connected, recommendations are usable, and the team has a repeatable review path.
Hosted Mode
Section titled “Hosted Mode”Hosted mode is the EcoScale cloud/SaaS distribution. Cluster and workload access are scoped by tenant and user context, which keeps multi-cluster and multi-team environments separated inside the platform.
Readiness Checklist
Section titled “Readiness Checklist”| Area | What to confirm | Why it matters |
|---|---|---|
| Cluster visibility | The target cluster appears in EcoScale. | Recommendations need the correct cluster context, especially in multi-cluster environments. |
| Workload discovery | Workloads appear with target references. | Operators must know exactly which Kubernetes object a recommendation affects. |
| Metrics history | Recommendations are populated for selected workloads. | Resource guidance depends on observed behavior. |
| Cost configuration | Pricing is configured when savings estimates are needed. | Financial prioritization depends on realistic CPU and memory pricing. |
| Change permissions | Apply actions are available only to the right users. | Resource updates mutate Kubernetes workloads and should be controlled. |
If any of these checks fail, resolve visibility and data quality before applying recommendations or enabling automation.
In These Docs
Section titled “In These Docs”Use Workload Optimization for workload discovery and prioritization. Use Recommendations for CPU and memory guidance. Use Automation only after manual review has produced predictable results.