@Mason Menges sure, i understand that it’s not necessarily an issue that’s stemming directly from prefect,
and - yes - i am already specifying the resource request in my run-config
it didn’t seem to matter (e.g. i requested 1gig memory and 1 cpu when the quota was like 50gig memory and 10 cpu) and (apparently) it just blocked the job from submitting
i think the issue i have with prefect here is that (according to K8s specs at least) if you try to provision a job in k8s that doesn’t meet the quota, you’re supposed to get blocked (i.e. get an error).
there was no such error here, just spinning forever until it gets picked up by lazarus once, twice and finally a third time
i would expect to see some error message if the issue was the quota, but then again, it works perfectly without the quota in place…
my devops is set to work on this again tomorrow so i’ll report here if we figure something out.