This section describes the Kompass compute optimization solutions:
Headroom reduction: Cut costs by reducing overallocation and ensuring application availability, while still delivering on your SLA.
Pod rightsizing: Cut costs by matching Pod resources to real-time usage at the container level—no restarts or manual tuning—while still delivering on your SLA.
Adaptive Pod placement: Cut costs by optimizing Pod placement to increase the likelihood of autoscaler-driven node scale-down.
Manage EKS clusters
To see and manage EKS clusters, be sure that you’ve integrated an AWS account for Kompass use with EKS permissions. For more information, see Integrate and onboard an AWS account with Zesty.
Compute solutions supported environments and limitations
Headroom reduction supports these environments:
Supported | |
|---|---|
Environment | AWS Elastic Kubernetes Service (EKS), v1.28 or later. From v1.33, in-place Pod vertical scaling is supported. |
Resource provisioning |
|
Cluster | IAM role for Service Accounts (IRSA) |
Autoscaling | HPA, KEDA |
Headroom reduction cannot be applied to:
workloads linked to node pools that have only GPU instances configured
workloads linked to node pools that have a Bottlerocket image configured
workloads where Pod rightsizing is applied
Pod rightsizing and Adaptive Pod placement support these environments:
Supported | |
Environment | AWS Elastic Kubernetes Service (EKS), v1.28 or later. From v1.33, in-place Pod vertical scaling is supported. |
Cluster | IAM role for Service Accounts (IRSA) |
Workload types | Deployment, StatefulSet, DaemonSet, Argo Rollouts (canary or blue-green strategies) |
Pod rightsizing generates recommendations only for the resources that have requests configured: CPU, memory, or both.
Pod rightsizing cannot be applied to:
workloads where the Headroom reduction solution is applied
workloads of these types: Jobs, cronjobs, or Replicasets
See also: