Need. More. Server. Need. More. POWER!!!
Just a bit more, maybe quite a bit more, to run services that are more CPU-intensive than those already running in the current Single-node Kubernetes cluster on an Intel NUC: lexicon.
That old house with aging electrical wiring, where last winter we needed Continuous Monitoring for TP-Link Tapo devices to keep power consumption in check at all times, could do with a more versatile and capable setup, to at least partially automate the juggling involved in keeping power consumption within the contracted capacity.
Home Assistant should be a good way to scale this up, but what that old house needs in the first place is a 24x7 system, so here we go again to setup a brand new Raspberry Pi... enter Alfred, the new housekeeper.
Upgrading the single-node kubernetes cluster on rapture
went smoothly, so it's time to repeat the process on lexicon, especially
since the current version (1.26) will be
End Of Life next month!
The old UniFi Controller and its required Mongo DB have been a bit
of a hassle to keep updated while running directly on the host OS in
my little homelab server,
so the time has come to migrate this to the new
linuxserver.io/docker-unifi-network-application
on my little Kubernetes cluster
on my new Kubernetes cluster.
Warning
Beware of outdated documentation, most articles out there like Install Unifi Controller on Kubernetes, are based on the deprecated linuxserver/unifi-controller, while others like setting up the UniFi Network Controller using Docker are using jacobalberty/unifi-docker which was quite outdated until recently.
Navidrome is a self-hosted, open source music server and streamer. It gives you freedom to listen to your music collection from any browser or mobile device I heard about in the Linux Matters podcast.
I tried it on my little Kubernetes cluster and here are impressions so far.
Always follow Kubernetes setup step carefully!
Forwarding IPv4 and letting iptables see bridged traffic is not optional; even if it looks like it.
Skipping that crucial step that takes a few minutes eventually led to wasting over 3 hours troubleshooting a issue that, apparently, nobody has ever solved on the Internet before. Naturally, because nobody should ever need to.
Last month I took a look at checking deployments before upgrading kubeadm clusters and found results mostly reassuring.
As a practice run to upgrade more complex setups, lets upgrade the cluster running on the desktop PC, which is only running a Plex Media Server (which recently become unresponsive) and the PhotoPrism® photo album (which never worked well enough to be critical to me).
PhotoPrism® is an AI-Powered Photos App for the Decentralized Web I heard some good comments about. I tried it on my other Kubernetes cluster and here are impressions so far.
I've been meaning to upgrade Kubernetes ever since Kubernetes Certificate Expired about a year after setting up the Kubernetes cluster in lexicon.
One day, completely out of nowhere, both download and upload speeds dropped to about 12 Mb/s flat, suggesting the speed was being throttled very much intentionally:
