Skip to content

2026

Self-hosted Personal Dis-Organizer with Vikunja

There is always too much to do and too little time, it never gets all done so the real challenge is to get the right things done at the right time, just to avoid Unforseen Consequences...

In one more attempt at getting better organized than having lots of browser tabs always open, emails unread in the inbox and, worst of all, uncountable ideas floating in the brain with nowhere to rest, lets try Vikunja, the fluffy, open-source, self-hostable to-do app.

Upgrading a single-node Kubernetes cluster to Zero Downtime Maintenance

Ever since the new, more powerful octavo replaced the good old lexicon server as the single-node Kubernetes cluster to serve all the local self-hosting needs, the latter has not found any use. Since it would be a waste to let it sit in a box unused, it will be setup to join the (for now) single-node cluster that is octavo to enable Zero Downtime Maintenance.

Migrating Kubernetes volumes to Longhorn

Migrating NFS volumes to the NFS CSI driver was an easy step forward preparing the single-node Kubernetes cluster to be upgraded to an Active-Active High Availability cluster. The next step in that direction is to migrate volumes currently implemented (the lazy way) with hostPath pointed to local NVMe SSD storage to a distributed file system, while still leveraging the SSDs speed as high-availability distributed volumes replicated across every node's local NVMe SSDs.

Migrating NFS volumes to the NFS CSI driver for Kubernetes

NFS volumes have been mounted the lazy way as hostPath volumes, with the entire NFS volume being mounted by the host OS. While this works well enough in a single-node cluster, it wouldn't work well in a multi-node cluster and is just not the proper way to mount NFs volumes in Kubernetes.

For a better, safer and more efficient setup, NFS volumes will now be mounted using the NFS CSI driver for Kubernetes.

Upgrading single-node Kubernetes cluster on Ubuntu Studio 24.04 (octavo)

Upgrading the single-node kubernetes cluster on lexicon went smoothly, so it's time to repeat the process on octavo and alfred, especially since the current version (1.32) will be the next one up to go End Of Life in Feb 28, 2026 and a preemptive Kubernetes Certificate Check reveals certificates are due to expire by Feb 22 on alfred and April 26 on octavo.

Checking deployments before upgrading kubeadm clusters again found results mostly reassuring for version 1.34.