Roadmap

Ships in v0.2

• Greenfield hub install via install-hub.sh on Rocky Linux 10
• Registry sites and FleetClusterJoin clusters from the console or umkim CLI
• Site edge.ingress[] (port_forward / reverse_proxy) plus optional hubGateway; clusters bind with ingressId
• FleetApp Helm installs on a Ready cluster you select — capability candidate filters, no placement engine
• FleetChart library (publish OCI or upload charts to Harbor)
• fleet-edge routing (hub / site / none) and optional ACME + Authelia
• Cluster operations: node add/remove/replace, single-node nfs_local RWX, KubeVirt platform enable, VM power/console, operation history
• Optional YAIDAP provisioner connector: native Ansible inventory on hub, VM create, bare-metal install, hardware discovery
• Capability filters: umkim cluster candidates --require gpu,kvm,network.multus_l2,…
• Console Apps workflow and role-based RBAC (no org tenancy)
• Cluster delete defaults to detach (preserves spoke K3s and workloads)
• Hub backup/restore scripts (K3s SQLite, WireGuard, ACME, optional Harbor PVCs)

Removed since v0.1

• DCM control plane and catalog placement
• k8s / helm / kubevirt service-provider install paths for charts
• Sibling service-provider repos as a hub-install requirement
• Organization tenancy model
• route.mode: dual (use hub or site separately)
• Site-wide exposure_mode (replaced by ingress rows + hubGateway)

Explicitly TBD

• Active–active multi-cluster serving behind one hostname
• Automatic placement / rebalancing of FleetApps across clusters
• Nested workload clusters via KubeVirt + K3s on hypervisor parents
• Productized multi-cloud automation beyond the reference Ansible + console path
• Production-grade HA/failover, tenancy, and upgrade guarantees
• Complete application lifecycle and catalog as a finished product

Where to follow work

Source of truth for behavior is the umkim repository and the docs site. Version pins live in the repo VERSIONS.md. v0.1 docs remain available under /0.1.0/ on the docs site.