UnicornTranscoder VS client-go

Just having support for a remote transcoder, along the lines of unicorn transcoder or rffmpeg would be a good first step to let us start homebrewing a solution.

There's this project - https://github.com/UnicornTranscoder/UnicornTranscoder That lets you use a remote transcoder, but idk if the project is maintained anymore.

There are some projects to distribute transcoding jobs like the Unicorn Transcoder (last activity in 2021), Remote Transcoder (last activity in 2017) or the Kubernetes project (last activity in 2020)

Interesting, I wasn't aware they tweaked it so much. Projects like Unicorn Transcoder made it seem like you could just drop-in replace it with a different binary.

There was/is a Project for remote transcoding, the Unicorn Trancoder which might help but the last commit in that project was made in Oct. 2021.

On the other hand, there is a Project called Unicorn Transcoder which is to offload the transcoding job on a different machine. If that works with plex optimization or just the "on-the-fly" transcoder, I don't know.

Controller-runtime uses the client-go/util/workqueue library to implement its underlying reconciliation queue. In the package's doc.go file, a comment states that the workqueue supports these properties:

client-go is the official Golang client for Kubernetes, responsible for interacting with the Kubernetes API server using REST API. In fact, client-go can do almost anything, not just for writing operators. Even the internal implementation of kubectl is based on client-go. As for more specialized frameworks used to write operators, including controller-runtime, kubebuilder, and operator-sdk, they will be introduced later in this series.

The Kubernetes clients (e.g., Go client) support developers with both methods to connect to a cluster, as we can see in the following examples.

My suggestion would be to start looking at things like https://github.com/kubernetes/client-go first in order to get a feel for the API and how data plane k8s components interact with the apiserver (it's the same thing that kubelet uses). Then move on to trying to build your own k8s operator to get a feel for how people expand and customize k8s functionality without having to modify upstream at all. IMO the codebase itself is too messy and in constant flux to make too much sense of it unless you are planning to contribute to upstream.

GitHub related issue https://github.com/kubernetes/client-go/issues/735

CUE is cool and all but as soon as I start writing real code structures I want to reach for client-go.

I looked at dynamic package, but it seems like it needs GroupVersionResource, which is different for, say, Service objects and Deployment objects. Also when I pass schema.GroupVersionResource{Group: "apps", Version: "v1"} it doesn't find anything, when I pass schema.GroupVersionResource{Version: "v1"} it finds only namespace object and also doesn't looks for labels, though I provided label options:

I'm writing a script that uses the k8s.io/client-go library (godocs here) to manipulate Deployments. In particular, I want to add a label selector to every Deployment in my cluster. Deployment label selectors are immutable. So my approach is to: