alt Hacker NewsI'm curious from the other direction; where do you see overlap between k8s and what's described on the Superlogical website?
Replies
> For us, that means interactive work, automatic work, and production work would share one well-crafted underlying system instead of living in separate tools.
Unless this is only for the narrow band of purely local work, I would be surprised if k8s didn't play a big role in the backend solution. It is the standard "well-crafted underlying system" for automatic production work. But, it isn't strong in the interactive-work/frontend aspect or other aspects, so it certainly wouldn't be the main focus of the final product.
Random example: you want to multiplex some work across multiple (self-hosted) agents, using niche fine-tuned models. It would make good sense if those agents were automatically provisioned and deprovisioned (and isolated to your subtenant), and k8s is a great underlying system for that sort of thing.
Doesn't K8s already practically provide a layer of abstraction across all infrastructure? You might not think of it as being a session, but to the degree that it's responsible for managing scaling and failover, it kind of is.
This isn't a statement of value, I'm genuinely curious myself. In fact, I bet this new thing will probably be better.