kubebuilder VS Radarr

The Spin operator uses the Kubebuilder framework and contains a Spin App Custom Resource Definition (CRD) and controller. It watches Spin App Custom Resources and realizes the desired state in the K8s cluster. Aside from the immediate benefits gained by running Wasm workloads in k8s, additional optimizations such as Horizontal Pod Scaling (HPA) and k8s Event-driven Autoscaling (KEDA) can be achieved in a pinch.

kubebuilder: brew install kubebuilder

The operator that I've been working on is designed to manage the full lifecycle of a QuestDB database instance, including version and hardware upgrades, config changes, backups, and (eventually) recovery from node failure. I used the Operator SDK and kubebuilder frameworks to provide scaffolding and API support.

Recently, I've been spending a lot of time writing a Kubernetes operator using the go operator-sdk, which is built on top of the Kubebuilder framework. This is a list of a few tips and tricks that I've compiled over the past few months working with these frameworks.

Since we built our operator using the Kubebuilder framework, most standard monitoring tasks were handled for us out-of-the-box. Our operator automatically exposes a rich set of Prometheus metrics that measure reconciliation performance, the number of k8s API calls, workqueue statistics, and memory-related metrics. We we were able to ingest these metrics into pre-built dashboards by leveraging the grafana/v1-alpha plugin, which scaffolds two Grafana dashboards to monitor Operator resource usage and performance. All we had to do was add these to our existing Grafana manifests and we were good to go!

I wrote a CSI driver and some operators. I admire K8s, because you can find solution to almost any problem in the source code - API versioning, load balancing, request throttling, optimistic concurrency, security, and much much more. I recommend https://book.kubebuilder.io/ It is similar to Operator SDK, but without Openshift-specific stuff. It gradually introduces you to many k8s concepts, and follows design patterns that k8s uses internally.

A better way to write an operator these days is to use kubebuilder [1].

My complaint is that I have seen orgs write operators for random stuff, often reinventing the wheel. Lot of operators in orgs are result of resume driven development. Having said that it often comes handy for complex orchestration.

[1]https://github.com/kubernetes-sigs/kubebuilder

Movies: Radarr

I use Nginx for Sonarr/Radarr would I see any general performance benefit when loading their webpages in general? If so, what level of compression would be ideal for this case?

In the /r/selfhosted community Sonarr and Radarr are staples, but their code isn't particularly great and there are lots of bugs people just deal with. Radarr forked Sonarr, their interface is similar but they suffer from disjoint bugs.

There may be better places, since I've just stuck to the same one for years now (and don't need them often enough to look into alternatives), but I usually use either subscene or opensubtitles. There are also programs that can automate it like bazarr, but it requires you to also use Sonarr/Radarr.

Radarr: Automatically downloads movies.

Radarr is for movies. Sonarr is for TV shows.

- Sonarr & Radarr for sailing the sea / keeping those media libraries growing ( https://sonarr.tv/, https://radarr.video/ )

Two instances of Radarr (one for 4K and one for everything else) running on one of my Linux servers.

Just seen that Signal notification support has been added to the latest version of Radarr. Had a look at the documentation but there is no guidance on how to set it up. I found this which alludes to needing to spinning up some kind of a 3rd party application to proxy the notification to Signal....but nothing about how to set it up.