Skip to content

docs: cross-link federation docs with edge instance-provisioning architecture #157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
scotwells wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: cross-link federation docs with edge instance-provisioning architecture #157

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/compute/development/rfcs/workloads/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

<!--
Expand Down
4 changes: 4 additions & 0 deletions docs/enhancements/federated-deployment-scheduling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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`.
Expand Down
Loading