azure-k3s-cluster VS node-red

If anyone wants a ready-to-go Azure template to play around, here you go:

https://github.com/rcarmo/azure-k3s-cluster

(I tweak this every now and then since I both used it as a training sample for my customers/peers and as a way to run my own batch processes as cheap as possible)

The runtime controller is uwsgi, which acts as supervisor for all processes of an app _or_ embeds the right interpreter-it's pretty much perfect for that, as it also has a cron scheduler and an on-demand, fire-up-an-interpreter-upon-request mode.

As to the k3s stuff, it's all here: https://github.com/rcarmo/azure-k3s-cluster. I update this from time to time as I occasionally nuke the entire cluster and rebuild it (I use AKS for non-hobby workloads, but a single master is just fine for most of my stuff).

Thanks! Piku has been my go-to for dev environments, Linux IoT and general-purpose stuff for a long while now, as it is simpler to iterate (no container build cycles, no need for a registry, relies on rock solid nginx/uwsgi, etc.).

I usually start with that and then containerize as needed, but this time it was actually the other way around -- since I didn't know what Node-RED modules I'd need and didn't see much point in going beyond a single core, I just sidestepped my custom Node-RED containers* and pushed out a Node-RED deployment to a underused, single-core piku instance.

(FWIW, I have a running k3s setup with the Azure equivalent of spot instances, but Node-RED can't take advantage of that setup and I mostly wanted the GUI and higher-level abstractions. You'd be surprised how much mileage you can get from something like this...)

* - https://github.com/insightfulsystems/node-red