♻️ Update konk machine type

vcluster deployment mode needs 2 volumes per cluster (one for the
control plane, one for shpod), so we're switching to a smaller
machine type since that's quickly becoming the limiting factor
rather than CPU/RAM.
This commit is contained in:
Jérôme Petazzoni
2026-04-30 10:50:01 +02:00
parent 6f125e901d
commit 528f687898

View File

@@ -4,20 +4,21 @@
# 500 MB RAM
# 10% CPU
# (See https://docs.google.com/document/d/1n0lwp6rQKQUIuo_A5LQ1dgCzrmjkDjmDtNj1Jn92UrI)
# PRO2-XS = 4 core, 16 gb
# Note that we also need 2 volumes per vcluster (one for vcluster itself, one for shpod),
# so we might hit the maximum number of volumes per node!
# (TODO: check what that limit is on Scaleway and Linode)
# (the limit on Scaleway is 15 volumes per node; 8 on Linode apparently? seems low, to check!)
#
# With vspod:
# 800 MB RAM
# 33% CPU
#
# PRO2-XS = 4 core, 16 GB
# DEV1-XL = 4 core, 12 GB
set -e
KONKTAG=konk
PROVIDER=linode
PROVIDER=scaleway
STUDENTS=2
case "$PROVIDER" in
@@ -26,7 +27,7 @@ linode)
export TF_VAR_location=fr-par
;;
scaleway)
export TF_VAR_node_size=PRO2-XS
export TF_VAR_node_size=DEV1-XL
# For tiny testing purposes, these are okay too:
#export TF_VAR_node_size=PLAY2-NANO
export TF_VAR_location=fr-par-2