Cloud Setup
I rent quite a few nodes from various cloud providers, as a way to provide network isolation and data redundancy.
SM Cluster
These nodes, rented from Contabo, form a Kubernetes cluster entirely managed with Talos Linux. While Contabo is not the most reliable provider, it was the cheapest provider that Talos Linux images worked out-of-the-box with. I've also found having unreliable nodes is a low-stakes, low-effort way of testing resilience of high availability setups. These nodes primarily exist to serve content, or host software services that require greater stability or throughput than my home ISP can provide.
Read about how I set this up here.
Aespa nodepool
name | role | vCPU | RAM (GB) | Storage |
---|---|---|---|---|
Karina | control plane | 4 | 6 | 400GB |
Giselle | worker | 8 | 24 | 1.2TB |
Ningning | worker | 8 | 24 | 1.2TB |
Winter | worker | 8 | 24 | 1.2TB |
Red Velvet nodepool
name | role | vCPU | RAM (GB) | Storage |
---|---|---|---|---|
Seulgi | control plane | 4 | 6 | 400GB |
Irene | control plane | 4 | 6 | 400GB |
Wendy | worker | 12 | 48 | 1.6TB |
Joy | worker | 6 | 16 | 400GB |
Yeri | worker | 6 | 16 | 400GB |
Want to see the current state of this cluster? I host a public instance of Grafana here; check out my dashboards!
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
name | role | vCPU | RAM (GB) | Storage |
---|---|---|---|---|
Umji | control plane | 2 | 4 | 80 GB |
Eunha | worker | 2 | 4 | 80 GB |
Sinb | worker | 12 | 24 | 640 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 that I wouldn't want tied to my home IP address or any other personally identifiable information. They are mainly responsible for web scraping and p2p file sharing, and their workloads are designed in such a way that an immediate termination would result in minimal, if any, data loss.
members
name | vCPU | RAM (GB) | Storage |
---|---|---|---|
Miryo | 4 | 8 | 100 GB |
Narsha | 4 | 8 | 100 GB |
JeA | 12 | 32 | 200 GB |
Gain | 12 | 32 | 200 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
- Ailee (1vCPU/2GB RAM) rented from DeinServerHost