Ellis Tarn

@M00nF1sh any progress on prioritization here?

@armujahid, we made karpenter flexible to arbitrary tags, so you should be able to work around this. Still -- it would be great to have this feature in the lbc

@M00nF1sh any word on this one?

Hey @andrewsykim, what's the status of this effort? Seems fairly paused? Is there some documentation somewhere for sig-testing? I'm looking to make some improvements to the AWS e2e Cloud Provider...

I really like the idea event driven cluster autoscaling, but I'm not sure exactly how this might work. In fact, I'm not even sure I understand the e2e journey of...

re: https://github.com/kedacore/keda/issues/637#issuecomment-1033790013 FWIW, Karpenter v0.1.1 implemented exactly this: https://github.com/aws/karpenter/tree/v0.1.1/pkg/apis/autoscaling/v1alpha1. We found that the sticking point with users was finding useful signals to scale the node groups. >The tricky thing though,...

> @ellistarn Do you support `/scale` subresource so we could scale Karpenter pro-actively? We moved away from this approach, since we decided that the best signal for our customers was...

It doesn't rely on node groups and collapses the combinatorial node group expansion problem of cas. There are a ton of other minor points that make it generally more usable,...

This proposal is awesome. In Karpenter, we decided against the k8s metrics api due to this exact single-slot problem: https://github.com/awslabs/karpenter/blob/main/docs/DESIGN.md#prometheus-vs-kubernetes-metrics-api. I'm a little nervous about the idea of separating by...

The main challenge of specifying `max_pods` is that it must be done in a launch template's user data. In Karpenter, we launch *many* different instance types, which means we'd be...