Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[preview] Decrease preview env density #4750

Merged
merged 1 commit into from
Jul 8, 2021
Merged

[preview] Decrease preview env density #4750

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions .werft/values.dev.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,18 @@ tracing:
samplerType: const
samplerParam: "1"

# we hit the "max. 110 pods/node" situation pretty often with our current core-dev setup.
# the proper way to fix those would be to adjust the CIDR for workload NodePool which is a bit more work.
# as a workaround, we blow up our RAM requests to trigger scaleup earlier.
# Note: This only works because we tune down our DaemonSet's requests to near-0 (because DS pods don't trigger scalups!)
resources:
default:
# as opposed to 200Mi, the default
# we make static pods big enough so that 100 pods fill up the whole node (we ignore other DaemonSets here because they are quite small),
# and assume not all envs carry workspaces all the time:
# => 32Gi / 100 ~ 328Mi => 350Mi
memory: 350Mi

components:

agentSmith:
Expand All @@ -33,7 +45,7 @@ components:
# in preview envs, we never want DaemonSets not to be scheduled (because they don't trigger scaleup)
resources:
cpu: 1m
memory: 32Mi
memory: 1Mi

server:
replicas: 1
Expand All @@ -50,7 +62,7 @@ components:
# in preview envs, we never want DaemonSets not to be scheduled (because they don't trigger scaleup)
resources:
cpu: 1m
memory: 32Mi
memory: 1Mi

contentService:
remoteStorage:
Expand Down Expand Up @@ -148,7 +160,7 @@ components:
# in preview envs, we never want DaemonSets not to be scheduled (because they don't trigger scaleup)
resources:
cpu: 1m
memory: 32Mi
memory: 1Mi

wsScheduler:
scaler:
Expand Down