Sequence · K8s E2E happy path · time ↓

Kubernetes E2E sequence

User posts ImpVM and ImpNetwork; API persists to etcd; Operator watches, gets dependencies, patches Reconciling, dispatches to Agent which creates the Firecracker VM and wires Cilium IPAM, returns result, then Operator patches Ready (or Failed) inside an ALT and emits events/metrics.
IMP Kubernetes E2E happy path Sequence from kubectl POST through API, Operator reconcile, Agent VM create and network wiring, to Ready status and events, with alt branch for failure. User / kubectl kubectl apply Kube API + etcd /apis/imp.dev IMP Operator cluster-scoped IMP Agent DaemonSet Events / Metrics events.k8s.io · Prom POST ImpVM WATCH ADDED GET deps Operator dashed --> 201 + state PATCH Reconciling DISPATCH Create VM Wire network result ALT [Ready] [else Failed] PATCH Ready PATCH Failed Events + Metrics LEGEND HTTP API Return Async / Event Headline success
12 messages, 5 lifelines, 1 ALT fragment (2 regions). Dashed = return/async. Accent = headline success (DISPATCH→Ready). Self-loops = Agent internal VM/net steps. Dark variant uses paper #110b0a and accent #f03a22.