[zachdev1]

An agent scoped cloud is exactly what fixes some of those concerns though. from a security perspective, you either trust your multi tenancy implementation to isolate workloads from each other or you use a common isolation layer (which k8s already gives you). budget becomes a property of the per-agent cloud itself.

[bigyabai]

From a security perspective, multi-tenancy is not any less secure than the "turtle shell security" microservices approach. You still have access to virtualization, networking controls and finer-grained fixed-cost hosting that you control instead of delegating to an LLM.

[zachdev1]

kube api gives you auditing, events, rbac, across pretty much all layers of the infra stack. if the agent does something in a VM you have to figure out what happened. if it does something on the control plane, it’s obvious what happened. i agree with you that security is any issue either way (especially based on recent events) but doing it under the kube umbrella makes it easier to manage at scale

[ai_critic]

> if the agent does something in a VM you have to figure out what happened.

If you can't audit what users are doing on a Linux system you have no business pretending you can run a k8s cluster.

(k8s was a ZIRP-fueled evolutionary mistake for most of the industry.)

[zachdev1]

no one is saying you can’t audit a VM. it’s about where you should audit and place controls. the k8s control plane makes me care less about what’s going on in the VM.

hard disagree on your last point. k8s powers pretty much all clouds as we know it