Greg

remember, the kubeconfig to edit is the one inside the container you are in, and not the one in your client. this solution work for me @ralgozino

The chart at version 2.1.38, with this values.yml ``` global: labels: app: ingressmonitorcontroller ``` generates this kind of configuration inside the deployment: ``` monitoring, ingressmonitorcontroller, Deployment (apps) has changed: #...

@DylanGuedes this refactor im doing should enable the logic that was completely missing, and so, fix the problem that we were facing in the last pr. What do you think?...

@DylanGuedes is this still on/needed?

> > @DylanGuedes is this still on/needed? > > Sorry, I did a extremely poor job following this work. Since we fixed the docs this one isn't "needed", but it...

@igorbdl have you resolved? mine is creating a `m6g.12xlarge` without any reason and will not scale back. ``` Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource...

sadly i noticed its the standard way of working for karpenter. im always with the biggest node possible from AWS. ``` spec: expireAfter: 1h taints: - key: dedicated value: "runner"...

but i cant refuse consolidate after @tm-nadavsh `NodePool.karpenter.sh "worker" is invalid: [spec.disruption.consolidateAfter: Required value, : Invalid value: "null": some validation rules were not checked because the object was invalid; correct...

> @nohant what version of karpenter are you running, if its the latest(0.37.0) it seems like you have multiple misconfigurations, `expireAfter: 1h` should be inside spec.disruption WhenEmptyOrUnderutilized, not a real...