I've written a bunch of k8s operators in go (and rust more recently). That's how basically everyone working with k8s does once you reach a certain level of complexity.
I don't really understand, in fact, why you'd use yoke instead of just writing an operator with kubebuilder or kube-rs.
Writing your own operator is a lot of complexity when what you want to do is deploy a package.
Via Yoke's AirTrafficController, it's easy to define a package as a CRD and its implementation (a program that takes the CR and outputs the desired underlying resources) and the AirTrafficController takes care of the rest.
You no longer need to think about reconciler loops, figuring out any orphaned state, etc.
I don't really understand, in fact, why you'd use yoke instead of just writing an operator with kubebuilder or kube-rs.