ENV VARS:

export S3_REGION=eu-south-1
export S3_ENDPOINT=https://s3.eu-south-1.wasabisys.com
export S3_ACCESS_KEY_ID=GPDPCSW1IWY7I55O4X0V
export S3_SECRET_ACCESS_KEY=czXmW7BBTQsbzoEDsNdotEn998QJgpTie9daF7Bl
export PROVIDER=elemento

<aside> 💡

Into field user_data there is a lot of info, probably regarding user auth, keep an eye for future errors since i’m not saving it inside vm data

</aside>

Mapping flavors into specs inside Elemento Go lib

Here a set of elemento configs:

Helium → 1 vcpu - 0,5 GB ram

Neon → 2 vcpu - 2 GB ram

Argon2 → 4 vcpu - 4 GB ram

Argon → 6 vcpu - 4 GB ram

Kripton → 8 vcpu - 8 GB ram

Defaults for kops are Neon for Nodes and Argon for Control plane

CORRECT API functions that must pick only valuable data, body transparent to the other funcitons

<aside> 💡

CREATE the SCHEMA about the Elemento Go lib structure in draw.io

</aside>

Adding boot volumes to the nodes

You need to add these commands: --node-volume-size=64 --control-plane-volume-size=64

Example create config for volumes of 64 Gigabytes:

S3_REGION=eu-south-1 S3_ENDPOINT=https://s3.eu-south-1.wasabisys.com S3_ACCESS_KEY_ID=GPDPCSW1IWY7I55O4X0V S3_SECRET_ACCESS_KEY=czXmW7BBTQsbzoEDsNdotEn998QJgpTie9daF7Bl PROVIDER=elemento dlv --listen=:2345 --headless=true --api-version=2 exec ${GOPATH}/bin/kops -- create cluster --cloud=elemento --name=test.k8s --state=s3://test-kops --kubernetes-version=1.32.4 --zones=europe --node-count=3 --node-volume-size=64 --control-plane-volume-size=64 --network-cidr 10.0.0.0/24 --v=10
OR
kops create cluster --cloud=elemento --name=test.k8s --state=s3://test-kops --kubernetes-version=1.32.4 --zones=europe --node-count=3 --node-volume-size=64 --control-plane-volume-size=64 --network-cidr 192.168.100.1/24 --v=10