I am :) you still need a PVC for the db though. Granted I plan on now moving that to nvme block storage.

https://github.com/anthr76/infra/blob/29643b374c3186bf2de42947b80d490f62f57c5b/k8s/base/federation/lemmy/kustomize.yaml#L27

Firstly, awesome to hear you’re using bjw-s app-template helm chart. He’s my good friend and former coworker :)

I’m also doing what @seang96@exploding-heads.com is doing.

While I don’t consider this completed yet I have posted how I’m doing things so far

+1 to Trillium. I looked long and hard on this before settling on obsidian with the livesync plugin.

My personal gotcha with Trillium was that it required sqlite over something like postgres and that web based editors was less important to me.

I’m more of a Kubernetes the Hard way kind of person, but I think it can be suitable for certain production workloads. I’d trust a production workload on it way more then Docker Swarm

I agree with this. I think single node or not the industry is moving towards Kubernetes for container orchestration. Docker has showed their evil intentions and it’s time to leave them in the past. Even podman has native kubernetes manifest support (albeit limited last i checked) as @rs5th@lemmy.scottlabs.io pointed out there’s good avenues to take if you want to avoid the complexities of kubernetes like k3s.

Same here except for Kubernetes I use volsync and push my backups to rysnc.net

Very neat! I also considering writing a helm-chart with my close friend’s amazing helm library. In the end I decided against it since this is a pretty simple deployment as of today. Tomorrow I will clean up the Kustomize manifests and some CI with a non-federated config file and post it :)

I just use wireguard with VyOS. Simple and efficient

K8s + GitOps is surprisingly low maintenance for the benefits you get out of it.

This is pretty cool! I also run Kubernetes at home