Karpenter & Cluster Autoscaler
Karpenter and the Cluster Autoscaler are not recommendation sources. GreenKube reads them only to estimate how much released capacity really becomes removed nodes: the realization factor. The Karpenter NodePool heuristic (greenkube.nodepool) and its NodePool policy advice were removed in this release.
Realization context
Section titled “Realization context”The controller reads, read only:
- the Cluster Autoscaler status ConfigMap
kube-system/cluster-autoscaler-status; - Karpenter NodePools (consolidation policy, disruption budgets) and NodeClaims (claim → pool);
- Karpenter
DisruptionBlockedevents (a blocker: the pool’s factor is halved) andUnconsolidatableevents (reported, factor unchanged); do-not-disrupt/safe-to-evictannotations and blocking PodDisruptionBudgets;- with Prometheus, Karpenter’s consolidation metrics (decisions, eligible nodes, pool cost). Metrics that are not exported change nothing.
These feed the per-pool realization factor. Events that cannot be read (RBAC) are reported as “Karpenter events could not be read”, never as “no blocker”. HPA reads stay too: they feed the rightsizing evidence and the risk model.
Permissions
Section titled “Permissions”get/list on karpenter.sh NodePools and NodeClaims, and list on core events, all in the chart’s ClusterRole.
Configuration
Section titled “Configuration”impact: autoscalerHint: "" # none, cluster_autoscaler or karpenter, when detection cannot see it # realizationFactor: 0.5 # pin the factor for every projectionconfig.recommendations.karpenterEnabled and sources.settings["greenkube.nodepool"] are accepted and ignored since this release; the chart’s install notes name them (Upgrading).