Fleet model
This content is for 0.1.0. Switch to the latest version for up-to-date documentation.
UMKIM separates management infrastructure from workload clusters:
| Layer | Role |
|---|---|
| Hub | Runs K3s, OCM, DCM, Harbor, console services, and fleet controllers. It is not an OCM ManagedCluster. |
| Site | A FleetSite registry object for workload-cluster metadata and optional edge policy. |
| Workload cluster | An independent K3s server represented by an OCM ManagedCluster and provisioned through FleetClusterJoin. |
Clusters connect over the WireGuard management overlay. The hub uses OCM
ManifestWork to deliver platform resources, while DCM providers materialize
selected workloads on clusters.
Each workload cluster belongs to one site through its fleet.site label. The
seeded management site is reserved for the hub and must not receive workload
clusters.
This design is a v0.1.0 proof of concept. It does not establish HA, tenancy, or production operational guarantees.