Comment by pphysch

> 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.