Kubernetes

“Like in particular, like Kubernetes, I feel like it's like kind of worked okay for backend teams, but not so well for data teams.”

“Less layers of infrastructure, less layers of abstraction, make it a lot easier to work with. Like we don't use Kubernetes, for example, I would just directly launch these things and it's just been much easier to debug this way.”

“It's easy to conflate long running with CPU intensive, and these are kind of not the same thing, and actually a lot of Specifically agentic workflows. A lot of what you're doing is you're waiting. You're waiting on human in the loop. You're waiting on LLM. You…”

“See, bro, the first step was making sure you don't have to use Kubernetes, and that we kind of solved. Now we'll do the rest. Like, that's just it. Like you can run agents without Kubernetes or VMs.”

“I think a good analogy here is sort of, like, technologically, it's kind of, you want to be the Kubernetes of the world for the agent, but with much better DX and easier, easier to use.”

“I think there's a somewhat similar situation here with the caveat of saying, like, 10 times faster. Like, just day one, so much momentum around MCP. So much interest in this. And then also, 10 years of CNCF to sort of teach the developer community and the vend…”

“Dynamo has a set of components that A, tell you how to scale. It tells you how many pre-fill workers and decoded workers it thinks you should have. And also provides a scheduling API for Kubernetes that allows you to actually represent and affect this scheduli…”

“We think that the same benefits that apply for DX also actually apply for AX, which is why would you have an agent read through hundreds of Kubernetes files and, like, write YAML that's not even typed when it can basically make a couple of changes in a decorat…”

“Kubernetes is hard to manage. It's not built for burstiness and custom images and has a terrible developer experience.”