[preview] Decrease preview env density

[geropl]

No description provided.

[princerachit]

Should we have an equivalent change in the other file/(s) too?

[geropl]

Should we have an equivalent change in the other file/(s) too?

Are we deploying multiple preview environments to them? If yes: maybe. But let's start with the problems we know about.

[csweichel]

Why 500Mi? Is there some kind of calculation behind this akin to #4700 (comment)

[geropl]

No calculation as I assumed assignment of static pods to be too dynamic to reason about.

Let's try. To come as close as possible to the theoretical limit of 33 preview envs are goals are:

• don't consume too much RAM to drive node count up artificially
• ensure we never reach "max nr of pods" with static deployments

Thus we make them big enough so that say 100 pods fill up the whole node (we ignore the DaemonSets here because they are quite small).
=> 32Gi / 100 ~ 328Mi
If we choose 350Mi we're coming close enough it seems.

WDYT? @csweichel

[csweichel]

Sounds good to me. Let's do this

[princerachit]

Should we have an equivalent change in the other file/(s) too?

Are we deploying multiple preview environments to them? If yes: maybe. But let's start with the problems we know about.

Yes we are deploying multiple preview env to k3s ws cluster

[geropl]

Yes we are deploying multiple preview env to k3s ws cluster

But we're not having trouble with it atm, plus not all preview envs deploy to that cluster I recon. Let's wait until we have problems, we can quickly come back to this, then.