Photo by ThisisEngineering on Unsplash. Source: https://unsplash.com/photos/woman-in-black-and-white-jacket-sitting-in-front-of-computer-monitor-iQqRM0XJvn8 (Unsplash License).

Edera wants AI agent execution to stay on your own Kubernetes clusters, and it shipped three primitives to argue the case.

  • Each agent runs in its own microVM with a private Linux kernel, so network reach is cut below the guest.
  • Live snapshotting freezes a running agent with its state intact, then restores it where it stopped.
  • Copy-on-write forking clones a warm agent into isolated children that share memory until a write.
  • Kubernetes 1.37 already ships pod checkpoint and restore as alpha, so the platform is growing the same idea from below.

The cost case matters as much as the security one. A fleet of thousands of agents holds memory while it waits on a tool call or a human review. Read the full analysis.

By Ivan Tarin

Ivan Tarin is a Principal Product Marketing Manager at SUSE, where he owns go-to-market strategy and positioning for a seven-product cloud-native portfolio spanning Kubernetes, virtualization, storage, security, and observability. A former full-stack developer who shipped production code for enterprise and public-sector clients including U.S. national laboratories, Ivan translates complex infrastructure and AI technology into messaging that lands with developers, platform teams, and enterprise buyers. He has presented at KubeCon, SUSECON, and AWS Developer Week, and is currently pursuing an MS in Artificial Intelligence at the University of Colorado Boulder.

Leave a Reply

Your email address will not be published. Required fields are marked *

Get the next one before it is old news

Independent analysis of cloud-native infrastructure, Kubernetes and data centre economics. No vendor spin.