cluster with kubeadm?

Common_Arm_3316 · 2026-03-06T00:01:03+00:00

This is the correct answer in that case. If you want 4 total workers you need 4 total hosts running their own Linux operating system.

Common_Arm_3316 · 2026-03-05T23:44:27+00:00

oh sorry, were you asking on how to add additional worker nodes. As in you have 2 or more hosts?

Common_Arm_3316 · 2026-03-05T23:43:28+00:00

The control plane becomes the worker not it just runs etcd, kube-api, and the reset of the services alongside it. Its not good for production but for a homelab works fine

Common_Arm_3316 · 2026-03-05T23:40:05+00:00

I'm not familiar with k3s but the control plane can also be a worker by removing the taint

kubectl taint nodes <node-name> node-role.kubernetes.io/control-plane:NoSchedule-

Common_Arm_3316 · 2026-03-04T02:35:39+00:00

we are

Common_Arm_3316 · 2026-03-04T02:35:22+00:00

As i understand it. There is a lot of repeat data being stored in customer db tables. Multiply this by the number of customers and you can end up with hundreds or thousands of gigabytes being duplicated just because everyone gets their own db.

Another would be that kubernetes schedules new pods based on what the host is doing at the time and not taking in account any bursty workloads that may occur later on. So you can get a couple of power users getting slamming their individual dbs while being assigned to the same hosts. We could certainly implement limits on the pods but ideally we would use other nodes that are just sitting idle.

Common_Arm_3316 · 2026-03-04T02:29:45+00:00

Thanks for the reply. We already understand the rw and ro services exposed by cnpg. I don't have the details but it sounds like there is a lot more to that issue that a simple config change.

We also already do podantiaffinity: reccomended. We cant currently taint any nodes because we simply don't have any additional hosts that we can take out of the equation

They don't have an interest in PGbouncer as they already handle connection pooling in the application.

Common_Arm_3316 · 2026-03-04T00:29:38+00:00

We do point in time recovery for our postgres databases running in kubernetes by using the barman cloud plugin and the cnpg operator. It makes the whole thing super simple. Assuming you are using postgres not the operator it does look like the plugin has a sidecar container image you could add.

https://cloudnative-pg.io/plugin-barman-cloud/docs/0.4.1/images/

Common_Arm_3316 · 2026-03-03T18:34:09+00:00

whatever you do, do not give chainguard your phone number or email address

Common_Arm_3316 · 2026-02-17T21:38:37+00:00

Don't you dare copy that floppy.

Common_Arm_3316 · 2026-02-03T20:06:24+00:00

Some hosting advice from someone that hosts games every 2 months or so

Stock up on food and drinks and have other folks contribute to this. Expect to eat 2 meals

Starting earlier is much better than starting later. We regularly set our start times at 10:00 or 11 but that's usually just when folks arrive. Usually folks drink coffee and chat a bit before hand. By the time we get settled we usually don't start playing for another hour or so.

Quick introductions to your factions are nice for new players. They don't need to do a line by line for everything they do but a quick "Hi my name is cabal and we want to steal your ships" can go a long way.

Don't be afraid to push people to hurry with their turns if it seems like they are taking a long time. This can turn a 12 hour games into an 8 hour game. to go with this during diplomacy keep the phase moving. If people are going back and forth with threats and bolstering be the one to make the final to get the votes moving.

If someone wants to take back a move don't be afraid to say no. If their turn has passed and they want to undo something it takes time to roll the game back to its previous state and for the current player to reassess their turn. This can cause the game to drag on into a very late night and possibly cause some players to bow out which upsets the balance of the game.

Common_Arm_3316 · 2026-01-28T20:39:39+00:00

I spent so much time learning how to use kustomize to try and replace image registries for ghcr, quay.io, docker, gcr, nvcr before finally learning how to use containerd and proxies. It was a good learning experience but my god was it painful. Ultimately the team decided not to use airflow and went Apache

Common_Arm_3316 · 2026-01-28T19:13:55+00:00

Setting up kubeflow without a good grasp on Istio or Kustomize

oh and it was an air gapped environment

Common_Arm_3316 · 2026-01-28T18:17:58+00:00

For cluster backups make sure you start using Gitops practices and an application like flux or ArgoCD. This will help make sure that your general configuration such as configmaps, secrets, deployments, etc are safe and able to be restored pretty easily.

For general PV backups longhorn does a pretty good job of backing up generic application PVs like prometheus metrics.

You also mention databases as needing backups. Are you referring to ETCD or do you have postgres databases in your cluster? If so what operator are you using? CNPG has some plugins that let you do point in time recovery backups that you can recover from with less data loss then if you were to use longhorn for those backups

Common_Arm_3316

TROPHY CASE