Skip to content
This repository has been archived by the owner on Apr 11, 2022. It is now read-only.

feat: set cpu/mem requests and limits for prisma and cloudsql #298

Merged
merged 4 commits into from
Apr 12, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
12 changes: 12 additions & 0 deletions back/node_watcher/kubernetes/nodewatcher-deployment-staging.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,12 @@ spec:
ports:
- name: prisma-4466
containerPort: 4466
requests:
memory: "1280Mi"
cpu: "250m"
limits:
memory: "2560Mi"
cpu: "500m"
env:
- name: PRISMA_CONFIG
valueFrom:
Expand Down Expand Up @@ -54,6 +60,12 @@ spec:
"--dir=/cloudsql",
"-instances=test-installations-222013:europe-west1:kusama-etl=tcp:0.0.0.0:5432",
"-credential_file=/secrets/cloudsql/credentials.json"]
requests:
memory: "16Mi"
cpu: "250m"
limits:
memory: "32Mi"
cpu: "500m"
volumeMounts:
- name: cloudsql-instance-credentials
mountPath: /secrets/cloudsql
Expand Down
2 changes: 1 addition & 1 deletion back/server/kubernetes/server-deployment.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,4 @@ spec:
value: http://nodewatcher.nodewatcher-staging:4466
ports:
- name: nomidot-4000
containerPort: 4000
containerPort: 4000