hardyrekshin

joined 1 year ago
sorted by: new top controversial old
Migrating from multiple docker-compose VPS to Kubernetes in c/[email protected]
[–] [email protected] 1 points 1 year ago (1 children)

What's your take on inter-cluster communication?

E.g. I could hypothetically have 3 clusters:

  1. Administrative
  2. Web-Facing
  3. Backend

Potential use cases:

  • Backend might produce updated parquet files which needs to be transferred and made accessible on metabase in the Web-Facing cluster.
  • Web-Facing might need to send batched inputs (from webhooks for example) to Backend for processing.
Migrating from multiple docker-compose VPS to Kubernetes in c/[email protected]
[–] [email protected] 1 points 1 year ago

Good point about Tailscale. It hadn't occurred to me.

How does DNS work for a Tailscale-networked cluster of servers?

My understanding is at least one of the nodes would need to be designated as the ingress. I could potentially also have all the master nodes hold the ingress, but then I believe that means I'd need to use round robin DNS in cloudflare to ensure the domains are always pointing at the cluster.

Storage might be a problem, but being more cloud aware potentially means I can run DuckDB against minio to scan S3 objects when doing data-intensive tasks.

Migrating from multiple docker-compose VPS to Kubernetes in c/[email protected]
[–] [email protected] 1 points 1 year ago

I read into Docker Swarm, the community surrounding it is much smaller and there appear to be far fewer tutorials compared with k8s.

In addition to hosting the usual self-hosted applications that are often mentioned, I also do a good amount of processing of crypto and other financial data. Being able to more dynamically add/remove servers and have the containers automatically assigned / routed should at least in theory save me a lot of time administering the infrastructure.

1
Migrating from multiple docker-compose VPS to Kubernetes (alien.top)
 

Almost 3 years ago, I paid for a few VPSs on which I host a variety of services. (Vaultwarden, gitea, drone, meshcentral, metabase, gptresearcher, etc)

Interspersed among the VPSs are a series of data processing containers to handle crypto data.

With the contract coming up for renewal, I'm exploring how to separate the hardware from the software so I'd only need to deploy the container to a pool of servers, and the infrastructure decides on which server to run the container, correctly route incoming requests, and update cloudflare dns for containers which are meant to be oublicly facing.

I went through the kubernetes the hard way tutorial and have a cursory understanding of kubernetes but with some substantial gaps which I couldn't Google away.

For the replacement platform, I'm thinking to:

- Combine multiple VPSs as a baseline cluster to run internet-facing loads

- Use some home servers for backend/non-internet facing processes and make the data available on the Internet facing hosts.

- Add the ability to dynamically add more VPSs or preemptible instances from GCP/AWS

I'm still stuck on the first part. Standing up a kubernetes cluster using multiple VPS with different public IPV4 addresses.

Googling around heavily suggests this is not a common use case. Or at least I'm not using the correct terms.

Is there a better solution for me to pursue?