Clusters

Once connected, EcoScale discovers workloads, organizes them by namespace, and surfaces recommendations tied to the correct cluster context. This is essential in multi-cluster environments where workload names and namespaces are reused across staging, production, and regional clusters.

EcoScale works with major Kubernetes distributions including Amazon EKS, Azure AKS, Google GKE, Red Hat OpenShift, and conformant on-premises clusters.

Connecting a Cluster

Sign up or sign in to EcoScale, then go to Settings -> Clusters and select Add cluster. Enter a clear cluster name that operators will recognize in workload and namespace views.

EcoScale will show installation instructions for the agent Helm chart. Run the command in the target cluster context:

helm upgrade --install escale-agent-crds oci://r.ecoscale.dev/ai/escale-agent-crds \
  --version 0.3.0 \
  --namespace escale-system --create-namespace

helm upgrade --install escale-agent oci://r.ecoscale.dev/ai/escale-agent \
  --version 0.3.0 \
  --namespace escale-system --create-namespace \
  --set mode=readonly \
  --set cluster.name={name} \
  --set oidc.clientId=$CLIENT_ID \
  --set oidc.clientSecret=$CLIENT_SECRET

Replace {name} with the cluster name configured in EcoScale. Use the $CLIENT_ID and $CLIENT_SECRET values shown in the EcoScale cluster setup instructions. The readonly mode connects the cluster for visibility and recommendations without granting write-oriented behavior. Set hpa=true on the escale-agent-crds command only when HPA-related CRDs should be installed.

After the chart is installed, return to Settings -> Clusters and confirm that the cluster becomes visible. Once connected, EcoScale can begin organizing namespaces, discovering workloads, and surfacing recommendations when metrics are available.

For installation modes and RBAC configuration, see Agent Helm Chart.

Hosted Mode

Hosted mode is the EcoScale cloud/SaaS distribution. Cluster access is scoped by tenant and user context so multiple teams, environments, or customer accounts can use the same platform without sharing ownership or access boundaries.

In hosted mode, always verify the cluster before applying recommendations. The same service name may exist in staging, production, or regional clusters.

Connection Outcomes

Outcome	Meaning
Cluster visible	EcoScale can show the cluster in the platform and associate workload data with it.
Namespaces discovered	EcoScale can organize workload recommendations by namespace.
Workloads discovered	WorkloadScaler-backed inventory is available for optimization review.
Recommendations populated	Metrics and analysis are sufficient for CPU and memory guidance.

Clear cluster naming matters. Use names that operators can distinguish quickly, especially when reviewing changes that may affect production workloads.