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.
In an old house with aging electrical wiring and a limited power contract, keeping power consumption in check is quite necessary and can be a bit of a challenge. Some appliances are very power-hungry for short periods of time, at unpredictable times throughout the day, while others are running constantly and add up to a baseline that quietly takes a chunk of the power budget.
A decent way to keep an eye on power consumption is offered by the TP-Link Tapo line of products, in particular their smart plugs with energy monitoring and temperature and humidity sensors. These devices are relatively easy to setup, reliable, discrete and not too expensive... although they do add up fast!
For all the smart features in these devices and the companion app, there is no way to have a panoramic view of aggregated power consumption broken down by device, or to configure thresholds based on the aggregated power consumption from all appliances. Such panoramic view was not hard to implement by building on the Continuous Monitoring solution previously built for monigoring computing resources (already monitoring temperatures and power consumption).
The time has came to update my other PC, which I use also for gaming, coding, media production and just about everything, to Ubuntu Studio 24.04.
This is a smaller PC build based on a lower TDP CPU (AMD Ryzen 5 2600X) to fit in a Silverstone RVZ03 Mini ITX case with the very compact Noctua NH-L9x65 cooler.
After about a year since starting a blog with Jekyll on GitHub pages, the time has come to step this blog's game up. Jekyll is good, but it makes copying text a bit hard sometimes (hard to see) and code blocks are lacking some features like showing file names and highlighting specific lines. These features, and more, are available in Material for MkDocs, another Markdown-based documentation framwork that looks really good!
For a tutorial, see Material for MkDocs: Full Tutorial To Build And Deploy Your Docs Portal.
For more inspiration, see also Beautiful Pages on GitLab with mkdocs.
This would be a very minimal journey of installing Ubuntu Studio 24.04 on a relatively new mid-range Intel® NUC 13 Pro mini PC, had it not gone wahoonie-shaped...
The time has came to update my main PC, which I use for gaming, coding, media production and just about everything, to Ubuntu Studio 24.04.
Ubuntu Studio 24.04 LTS Released on April 25th but, as they themselves put it since it’s just out, you may experience some issues, so you might want to wait a bit before upgrading.
There doesn't seem to be anything particular scarey in release notes:
And my plan is not to upgrade in place; I like to keep the previous version around, just in case I need a stable system to fall back to.
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).