pull down to refresh

Hi everyone! 👋
This is my very first post on Stacker News, I recently joined to take part of the community (or should I say territories) and also give my contribute!
I have one "major" project at the moment that I would like to tell you about, even though it's a small thing: I want to migrate a Bitcoin stack I'm currently running on Docker on a spare Laptop to my self-hosted, flux-managed Kubernetes Cluster.
My BTC stack is here (it's a fork of an existing project) and includes:
  • bitcoind
  • electrum
  • tor
  • btcexplorer
  • lnd (which I personally added to the original repo)
The docker images are built from scratch and the idea is to compile the source code directly, when possibile.
All the heavy data is stored in a mounted NFS storage (example, the blockchain itself); while indexes and so on are on a local SSD.
Since I setup a home lab with a Talos Kubernetes Cluster on Proxmox, storage provided by OpenMediaVault and everything is managed by Flux (so gitops way), I wanted to move the whole stack to the k8s cluster and finally retire the old laptop. The (mirrored) repo I use for Flux is called (beehive)[https://github.com/fonzdm/beehive] (since I'm using BeeLinks mini-pcs for my cluster 🫡): you can take a look at the things I'm currently self hosting!
I would like to write some articles of this journey. The main roadmap is:
  1. Setup an internal private OCI registry where the images will be pushed
  2. Create a pipeline to automatically build and push the images
  3. Uplift the stack version (I have to finally take a choice on the Core v30 matter... sigh 🤢)
  4. Develop helm charts (or just stick to plain K8s template) for the various services
  5. Deploy the stack on my cluster using Flux
I can't wait to start and write about this, hope you will find interesting and exciting as I do! I hope to have selected the right territory; if not, please I kindly ask for a better one to post this and the upcoming articles!
Feedbacks welcome!
\FonzDM 📝