Cloud Setup

I operate multiple Kubernetes clusters across cloud and on-prem environments, deliberately segmented by trust level, network exposure, and failure tolerance. These clusters host production-facing services, observability backends, CI/CD infrastructure, and disposable scraping workloads.

LOONA Cluster

All nodes below are ARM64 instances rented from Netcup for testing workloads ahead of an Ampere hardware purchase—I transitioned from Contabo to this setup for better reliability.

These nodes primarily exist to serve content, or host software services that require greater stability or throughput than my home ISP can provide.

memberrolevCPURAM (GB)Storage (GB)
haseulcontrol-plane14321024
kimlipcontrol-plane14321024
yvescontrol-plane14321024
heejinworker14321024
hyunjinworker14321024
yeojinworker14321024
viviworker14321024
jinsoulworker14321024
choerryworker14321024
chuuworker14321024
gowonworker14321024
hyejuworker14321024

Viviz cluster

This is another Kubernetes cluster set up with Talos Linux. It handles all http requests from the "outside world" (including this website!)- no critical data is stored on these nodes. These nodes are rented from Hivelocity.

members

namerolevCPURAM (GB)Storage
Umjicontrol plane2480 GB
Eunhaworker2480 GB
Sinbworker1224640 GB

Brown Eyed Girls cluster

I also have a few miscellaneous VPSes that I am renting from multiple providers throughout the EU and Asia. These nodes are responsible for workloads designed to tolerate node termination and avoid coupling to a single provider or identity.

members

namevCPURAM (GB)Storage
Miryo48100 GB
Narsha48100 GB
JeA1232200 GB
Gain1232200 GB

Soloists

I maintain one bootstrap node, running docker in swarm mode, that provdes Talos configuration and DNS information for custom domains. As a single point of failure, it's on my list for finding an alternative implementation, but it's utilised so infrequently it'll be rare that an issue occurs.

members