So, after fiddling with more cloud native and serverless stuff in the last week or so, I pivot back and fire up my on-cloud Kubernetes stuff to discover they are ... not working. The actual neat thing is after an obscure error, the starup scripts contine a bit and then abruptly stop.

My inkling after doing a bit of googling is that the repo providing Kubernetes has ceased providing support to older versions of Ubuntu, and I'll have to do some microsurgery there to get it working.

I already have some work I wanted to do on other updates, and I wanted to do one more commit on my current fork before creating a new project; mainly because the main upstream is in archive mode and the upstream of me doesn't seem to be maintained either. With that said, I don't know how much effort I can put into maintaining this, and how worth it is compared with just using a load balancer -- but I'd at least like to try bringing it up to date. I think running through the costs of LB versus K8s on a budget is a good article and video.

As an aside, I tried setting up SAM as a Lambda environment locally, but the OS I chose used Python 3.5 and the SAM env was using 3.8, and the "build" command is fussy and wants a minor version match. Setting SAM to 3.5 made it mad, and trying to upgrade to 3.8 locally refused to work. I tried some other variations, but so far haven't found a match. If worse comes to worse, I'll find an OS with a recent Python that SAM supports.