javascript VS controller-runtime

https://github.com/kubernetes-client/javascript

Full disclosure I haven’t tried this but I’m curious if you have. The main component of a controller is its k8s client, so go will always have an advantage, but this JS client looks somewhat decently maintained

kubectl -n my-ns create job --from=cronjob/my-cron-job my-job using javascript kubernetes-client ?

async/await did exist two years ago. Maybe they wanted to be consistent with even older examples. I dunno, every single thing Google-related uses promises, so I'm thinking they're partial to that for some reason.

Another example from 4mo ago: https://github.com/kubernetes-client/javascript/blob/master/...

The front end responsible for displaying the JSON results is written in vanilla JS (HTML5 charts) but I haven't written anything that interacts with the API yet. I see there is a Javascript Kubernetes Client.

operatorpkg is a set of packages used to develop Kubernetes operators at AWS. It contains opinions on top of existing projects like https://github.com/kubernetes/apimachinery and https://github.com/kubernetes-sigs/controller-runtime. In many cases, we plan to mature packages in operatorpkg before commiting them upstream.

however, at least in envtest this returns

(rejected) kubernetes-sigs/controller-runtime #2266 🐛 Support get config inside snap with SNAP_REAL_HOME

Check out https://github.com/kubernetes-sigs/controller-runtime/blob/main/pkg/client/example_test.go. It really is that easy :-).

I am using Kubernetes controller-runtime envtest.