From 508591659db007a09cdd128c9ee605d94b8f9fd9 Mon Sep 17 00:00:00 2001
From: Scot Wells <wells.scot@gmail.com>
Date: Thu, 11 Jun 2026 10:45:28 -0500
Subject: [PATCH] docs: cross-link federation docs with edge
 instance-provisioning architecture

Point readers from the federation/control-plane docs to the unikraft-provider
doc covering how edge locations turn Instances into running unikernels.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---
 docs/compute/development/rfcs/workloads/README.md    | 2 ++
 docs/enhancements/federated-deployment-scheduling.md | 4 ++++
 2 files changed, 6 insertions(+)

diff --git a/docs/compute/development/rfcs/workloads/README.md b/docs/compute/development/rfcs/workloads/README.md
index 8d7ab8a9..0ec00225 100644
--- a/docs/compute/development/rfcs/workloads/README.md
+++ b/docs/compute/development/rfcs/workloads/README.md
@@ -653,6 +653,8 @@ sequenceDiagram
   WorkloadDeploymentScheduler-->>Controller: Return (no requeue)
 ```
 
+Once a `WorkloadDeployment` is assigned a location, the compute operator at that location creates the individual Instances. How an edge location turns these Instances into running unikernels — host assignment, networking, and boot via Kraftlet — is documented in [Instance Provisioning via Kraftlet](https://github.com/datum-cloud/unikraft-provider/blob/main/docs/enhancements/instance-provisioning.md) in the unikraft-provider repository.
+
 ## Production Readiness Review Questionnaire
 
 <!--
diff --git a/docs/enhancements/federated-deployment-scheduling.md b/docs/enhancements/federated-deployment-scheduling.md
index be2e0dde..fec3a3d5 100644
--- a/docs/enhancements/federated-deployment-scheduling.md
+++ b/docs/enhancements/federated-deployment-scheduling.md
@@ -165,6 +165,8 @@ sequenceDiagram
     CPC->>Project: write Workload.status
 ```
 
+The POP cell steps above are summarized from the federation perspective. How an edge location turns these Instances into running unikernels — Kraftlet picking up each Instance, wiring up host networking, booting the unikernel, and reporting status back — is documented in [Instance Provisioning via Kraftlet](https://github.com/datum-cloud/unikraft-provider/blob/main/docs/enhancements/instance-provisioning.md).
+
 ### Deletion Path
 
 ```mermaid
@@ -242,6 +244,8 @@ A new controller in the Control Plane Cell:
 - Updates local `WorkloadDeployment.status` with aggregate replica counts (Karmada aggregates this back natively).
 - **Remove**: `WorkloadDeployment.status.location` (location is now implicit in `spec.cityCode`).
 
+The edge-side path from a created `Instance` to a booted unikernel — host assignment by the Unikraft Provider, networking, and boot via Kraftlet — is covered in [Instance Provisioning via Kraftlet](https://github.com/datum-cloud/unikraft-provider/blob/main/docs/enhancements/instance-provisioning.md).
+
 ### `InstanceReconciler`
 
 - **Runs in POP cell operators** alongside `WorkloadDeploymentReconciler`.