Taylor Silva

> I wonder if there is a way to make this somehow customizable / easy to experiment with different notions of overload, while at the same time keeping the default...

> Maybe the load estimation should not be based on the last 30s, but more on something like an exponentially weighted moving average, see for example https://github.com/VividCortex/ewma. Great suggestion! Maybe...

That's a good thought. Right now I'm building it out with `overloaded` being a separate field on the worker. I think I'm going to stick with that and not add...

@drahnr In case you're still stuck, you can reproduce locally by running: ``` go test -v ./worker/runtime/spec ``` I got the same result as what's in CI ``` ┌─[drahnr/master*][~/workspace/concourse/concourse] └─▪...

Looks like your `undo` commit fixed all the unrelated stuff :)

Just got around to trying to reproduce this and I still can't!!!!?!?! Followed your setup; minikube version v1.17.1 and k8s 1.20.2 with chart 14.6.2 using default values.yml. - I modified...

Let's do it! I'm good with slack, though if you're on discord you could also join the Concourse discord server. The entire team is always hanging out there: https://discord.gg/MeRxXKW

Was able to reproduce it, the difference was `--driver virtualbox` when starting minikube. Missed that note when I first tried reproducing.

@chenbh mentioned this looked similar to https://github.com/concourse/concourse/issues/6038 We updated our pipeline to use the ubuntu based version of the git-resource: ```yaml resource_types: - name: git type: registry-image source: repository: concourse/git-resource...

@srheaume Besides virtualbox, what other k8s environments are you seeing this issue in? GKE? EKS? other cloud providers? See Daniel's comment above^ --- I tried reproducing on GKE `v1.18.12-gke.1210` but...