Humans, Robots, and Kubernetes

Fun hands on use-case/story. Trying to connect sensors & actuators sounds fun! It's clear that they need some kind of infra/platform that they can run on-prem, & this feels like a lock.

There's a new Dynamic Resource api in k8s 1.26 that feels potentially well suited to managing their various kinds of node-attached resources in a pretty broad/generic/cloudy way. Taking the cloud from anonymous compute/storage nodes to an all encompassing management system for whatever we have is an interesting next step. I rather doubt we'll see folks like this spend the 3x effort to pioneer use of these abstractions but over time it should start to emerge & become more regular. https://kubernetes.io/docs/concepts/scheduling-eviction/dyna...

There's also a really neat really nice CNCF Sandbox project Akri which performs semi-similar-ish functions as Dynamic Resources. One of the examples they use as a goto is managing a fleet of OVNIF cameras, like, security cameras. https://github.com/project-akri/akri

On another topic, appreciate this article talking about the mixed human/robot workflows. Good to consider! I worked at a great & interesting data-warehouse company a long time ago that had some very complex long running ETL pipelines & limited compute resources (good number of boxes... pre-cloud era!), and a lot of time-sensitivity. The company used Jira to manage the ETL end to end, with custom workflows where work would gate, process, get checked through various stages, with processors updating the ticket as work advanced or to report % complete. Intensely sharp choice not to build it ourselves, to use a tool for tracking work, even though the code (robots) we built were doing 9/10ths the work. Fun to see a similar topic discussed here.

Good problem setup, interesting view here. Would appreciate a little more technical specifics, but still fun to see.