Skip to content
UMKIMDocs
Search limited to 0.1.0. Switch to the latest version for up-to-date results.

Cluster creation scope

This content is for 0.1.0. Switch to the latest version for up-to-date documentation.

The public v0.1.0 path creates workload clusters through authenticated FleetClusterJoin workflows after the hub is installed. Each cluster runs an independent K3s server, registers with OCM, and can receive the k8s, helm, or kubevirt provider.

Historical inventory-driven workflows are not a public deployment model and are intentionally omitted from this snapshot. Nested workload clusters remain outside the v0.1.0 supported scope.

UMKIM v0.1.0 remains an unsupported proof of concept regardless of the chosen cluster topology.