shapirus

Yeah sure. It looks like it's going to be an iterative process either way. Good thing is that we know how to reproduce it, so we have a way of...

...lots of failing checks on that PR :)

@ephesused since PR https://github.com/kubernetes-sigs/kustomize/pull/5076 has finally been merged, I decided to run my tests again. Unfortunately, there has been no release with that PR yet, so I had to build...

5.2.0 has just been released, and I can confirm that it is still as fast as the revision I tested in https://github.com/kubernetes-sigs/kustomize/issues/4569#issuecomment-1762786077.

> Experienced this on version v1.28.2 running on a 1.28 cluster. There was an EC2 instance created that never joined the cluster, causing the autoscaler to think unschedulable pods could...

Warm runners have one issue: they force the node that their respective pods run on to be running by preventing cluster-autoscaler from terminating the instance, which makes it impossible to...

It would also be nice to make it possible to "preheat" a pool of runners. For example: - we have a "heavy" runner set to run CPU and memory-intensive jobs...

> Closing this one since we are trcking it here [#3704](https://github.com/actions/actions-runner-controller/issues/3704) 3704 is the current ticket, it looks like you pasted a wrong URL.

/remove-lifecycle stale

/remove-lifecycle stale