Has anyone else noticed that the k8s_executor running dagster v0.14.20 doesn’t respect the max_concurrent parameter?
Could just be our deployment, but wanted to see if this was the case for anyone else
Think I found the bug in our code, ignore this 🙂