Drone-runner-kube slow to process spike in pipeline requests

I don’t have a great way to measure this at the moment TBH. Anecdotally, we typically see clone steps start with a few seconds of being triggered. Under load (but still within the DRONE_RUNNER_CAPACITY) this can start to take minutes. This is largely with available capacity, but I’m sure you’re also right that to some degree there are delays due to k8s scaling cloud infrastructure. We’ll start looking for better ways to measure these various indicators.