fubectl VS metacontroller

To anyone visiting here, I got a lot of feedback for new tools (which I haven't tried yet), both on Youtube and here, so I compiled it into a list: A comment on Lens: Initially I wanted to include Lens in the video but decided it's a bit different in that it's not a CLI / TUI. Many users shared bad experience with Lens, mainly around performance and a large amount of requests it shoots at the cluster API to a point where some companies banned it. These are the tools (I may add a video review on if anyone thinks it's worth it): * https://github.com/kubermatic/fubectl - for an improved kubectl experience * https://github.com/particledecay/kconf - for those with complex kubeconfig changes requirements * https://github.com/MuhammedKalkan/OpenLens - an open version of Lens (note the above before using) * https://github.com/hidetatz/kubecolor - colored kubectl output :) * https://github.com/astefanutti/kubebox - the K9s little brother? * https://github.com/bergerx/kubectl-status - human friendly resource status output

Check out Kubermatic’s fubectl: https://github.com/kubermatic/fubectl

Ah, I never heard about it. Ok, I saw it reduces repeated iteration that kubectl does https://github.com/kubermatic/fubectl But this is more on CLI enhancement, nothing to do really at the cluster side ..is it ??

It worth adopt proper controller development with something like Metacontroller, Kopf or Java Operator SDK.

There are many frameworks, like the Operator Framework (https://operatorframework.io/) to the MetaController (https://github.com/metacontroller/metacontroller) to KubeBuilder(https://github.com/kubernetes-sigs/kubebuilder) to the Kubernetes Operator Framework (kopf, https://kopf.readthedocs.io/en/stable/), among others.

You might like a little alternative to writing your own in the first instance:) take a look at https://metacontroller.github.io/metacontroller/

Codegen is not magic, but if you want to make it simple stupid, supportable and prod-usable I'd go for metacontroller. There's not much magic to it - just common admission/validation webhooks propagated to your controller implementation, alongside the simplest possible reconciliation cycle. We had adopted Knative driven metacontrollers and it's a pretty solid approach.

https://github.com/metacontroller/metacontroller - Sounds cool! I will look into it.

When I need a quick mutating controller, I like to use MetaController, which makes rapid prototyping really easy: https://metacontroller.github.io/metacontroller/

If you are more into lightweight and common use cases, look at metacontroller or the shell-operator.

In case you've not heard of it, the metacontroller aims to do exactly this. It provides the controller-lifecycle (registering your types, watching the API for changes, etc), you just need to provide a HTTP webhook to receive the JSON object, and respond with the modifications\resources you want.