@mprahl or @ralph: please take a look.

@csomh looks good to me. Any reason you picked 0.4 instead of a nice round 0.5 CPU limit? :)

That's a good question @mprahl! I have no clue :p

Right now I would guess that it came from the default CPU limit for
UpShift projects (300 millicores), increased with 100 millicores,
which made things 'feel' better.

I've quickly read through these
docs
again, but could not find anything about recommended strategies for
setting these limits.

FYI: I've noticed that the resultsdb DeployementConfigs were missing
CPU limits, so I've added those too. Better to be explicit about these
things, they say :)

Okay, still :thumbsup:

:+1:

If this is fine by you, I'll happily merge this after it's rebased to current HEAD. Let me know, from the comments, this seemed to be under development/discussion still :) Thanks!

@csomh is away for a few days. Let's wait for him to come back to see what he thinks.

This was rebased, it's ready to merge, @jskladan. Thanks!