andrii.k

[grafana.com](https://grafana.com/grafana/dashboards/) dashboard users can try [this](https://grafana.com/grafana/dashboards/23419-atlantis/) one too

We have an on-demand node pool with `expireAfter: Never` [(comment)](https://github.com/aws/karpenter-provider-aws/issues/7146#issuecomment-2543949261). Karpenter: 1.3.2. Testing Scenario: - Scale up an application Deployment to trigger a new Karpenter NodeClaim and wait for the...

Tuning [these](https://github.com/aws/karpenter-provider-aws/blob/release-v1.3.2/charts/karpenter/values.yaml#L157-L163) parameters significantly reduced node churn in our setup ([docs](https://karpenter.sh/v1.3/reference/settings/)). However, Karpenter still removes nodes with higher CPU and memory requests, even when there are nodes with much lower...