12 ms·
Off the top of my head I do not remember what the issue was (the changes to the code are from a month ago). Looking at the code now, `dockerExec` <https://githu
by megapixel99 2y ago
Off the top of my head I do not remember what the issue was (the changes to the code are from a month ago). Looking at the code now, `dockerExec` <https://github.com/Megapixel99/nodejs-k8s/blame/master/functions.js#L72 https://github.com/Megapixel99/nodejs-k8s/blame/master/funct...> uses `child_process` so that may have something to do with it... however, as I have said in other replies, I just wanted to learn more about the inner workings of k8s and I personally learn best when I create (or recreate) something, I doubt this project will take off, but if it does I will try to fix that when the time comes.
Regardless, thank you for the feedback.
- mst 2y agoI may read the source code to your project for fun. If you ever feel inspired to do so, I *really* wish somebody would write a decent way to do controllers in JS rather than golang (metacontroller is a lovely idea but somewhat limited in what you can build with it).
- scoodah 2y agohttps://github.com/kubernetes-client/javascript 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
- mst 2y agoI have not tried it currently, because I had so far completely failed to realise it existed. Muchas gracias and I'll have to have a look next time I'm in a suitably masochistic mood for k8s hackery.