I know you are joking but I am not sure if you are aware of how close you are to reality:

https://thenewstack.io/how-the-u-s-air-force-deployed-kubern...

Literally taking the software to the cloud

wow this is terrifying lmao

That's a bit overengineered, come on, really it just needs docker compose.

Or Erlang... oh wait, that would actually work. We don't want that.

A car built on Erlang would break down every 11 seconds but would immediately fix itself so you never notice anything's wrong.

Supervisors should set Check Engine.

Agree. I am not buying any car not running all software components as Spring Boot micro services in kubernetes cluster as a standard cloud native service.

If this setup can run my 95% uptime enterprise apps, I am sure as hell it can run my car too.

Most infotainment is already shit code. If same people use more tools the result will just be worse, if they can't even handle a monolith

Carbernetes. Now with reinvented wheel functionality.

and a few years later, we get Injecternetes … though I'm not sure if that will be the name of an improved fork… or the name of a security vuln exploit.

Lol. Reminded me of this - https://youtu.be/cfTIjuW6SWM

Fwiw - I am a kubernetes fan. Just not in cars.

If you're a k8s fan but don't consider it reliable enough to do anything even next to but independent from safety critical systems then that's not exactly a glowing recommendation.

Different tech has different needs. I can see it being really great with server side distributed systems. I don’t really see it having any benefit for running stuff in resource constrained single purpose environments

And yet it's true. Reliability never comes from unnecessary complexity.

Well Volkswagen/Cariad is certainly flirting with that idea. https://datatronic.hu/en/containerisation-in-automotive-indu...

Make sure to run at least 2 clusters in case one goes down

Watch us slowly reimplement Erlang on top of OCI.

Erlang but language independent is actually a solid pitch.

To be precise an incomplete, bug-ridden, undocumented reimplementation of Erlang.

I keep having to stop myself from implementing an incomplete, bug ridden reimplementation if half of Erlang on top of NodeJS so I see the attraction there.

Worker threads have a garbage API and I keep finding myself wanting to have n processes sharing m workers and there’s just no easy way.

I know you are joking but it’s actually not the worst thing in the world.

Can't wait to have to restart a kubernetes cluster to get sensor metrics from the engine to start again.

You'll need to replace your kubernator!