For one, the customer is entirely different. You are mostly serving data scientists who don’t have strong engineering skills, which dramatically skews the solutions toward things like Python and Jupyter.
This is a big reason why the tool space is different and has been successful at what it does.
Model training and serving are absolutely nothing like traditional methods. In serving, you are deploying a stateful model, not a stateless backend. That model’s state should ideally be continuously trained, requires different scaling and monitoring capabilities.
In training, the GPU problem is far from solved and it is unique to ML with things like how you shard models and fit their weights into memory.
There are extremely challenging problems in this space that simply aren’t the same as devops, and this is coming from a former k8s contributor.