Me!

I just finished a move from one Hetzner VM to another. The type of VMs are the same, in fact. It’s just that the new VM and all the software on it are entirely software driven. I kept logging my progress in my notes, copy pasting the plan from day to day and ticking things off. Now that it’s done and I still want to refer to it regurlarly, as the rest of the services come over, I wanted a place to keep it. And so this post, it is.

List of services that absolutely need to come over. Miscellaneous stuff later.

• the main domain
• the mastodon archive
• the email distribution list
• miniflux for rss feeds
• joplin
• baikal
• discourse (no more discourse!)
• markdown editor (hedgedoc)
• anki
• huginn
• syncthing
• IRC: theLounge + znc (see if we can make do with a single service now)

The Big Plan (Done! 🎉🎉🎉)

• The plan is to redo the cluster again and do my own instance of

• K3s

• Sealed Secrets

• Flux CD

• Certmanager (Not using it)

• Letsencrypt (using pre existing Letsencrypt certs)

• Get Traefik Ingress to work

• Figure out a way to get certs automatically into the cluster

• And once that is done, figure out an app to move (Miniflux or Hedgedoc?); 2025-12-03: Kanboard it is!

• Begin by moving (lifting and shifting in popular parlance) Kanboard to the cluster

• Cert will probably be needed (Wildcard cert works now, just like it does without the cluster)

• Convert a docker-compose to kubernetes manifests

• Learn how to configure an app with code

• Learn how to store data and back it up

• Figure out secrets, if there are any (for now sealed secrets ok, figure out vault and vault injection later)

• Learn how to tunnel through and reverse proxy

• Make Kubernetes manifests work with flux

• Figure out how to automate deployment of manual manifests

• Figure out how to migrate there if there is any in an old app

• Figue out how to automate updation of images in manual manifests

• Get another app (Miniflux) deployed

• Figure out what needs to happen as part of the lifecycle. What you want in the cluster, what stays out, do they intersect, how do updates of cluster happen? VM (node) updates as well?

• Then begin to think along the lines of Live Deploys. Prototype locally and once it works, migrate to production immediately

• Convert Kubernetes manifests to Helm Charts (optional, based on energy)

• Go live! Git is source of truth. Two repos.

• One for the Main node and its update

• Terraform will provision node and install package, setup firewall

• Figure out how to get Terraform to get the node talking to the git forge

• Structure repo, copy every thing node related there, and make sure stuff gets updated periodically and idempotantly, via ansible pull and a systemd timer

• The other one for k3s and flux

• Convert everything I have done locally to run on prod. Add more steps as you do them below

Feedback on this post? Mail me at [feedback at this domain](mailto:feedback@janusworx.com?subject=%22Feedback on post: The Big Plan: Change My VM to Be Gitops Driven %22).

P.S. Subscribe to my mailing list! Forward these posts and letters to your friends and get them to subscribe!