Skip to content

Glossary

Term Meaning
Hub Management-plane host running K3s, OCM, Harbor, console, and WireGuard
Workload cluster Independent K3s cluster registered with OCM
Site FleetSite logical location with edge.ingress[], optional hubGateway, and jumphost
FCJ FleetClusterJoin, the workload-cluster lifecycle resource
Overlay Private WireGuard management connectivity
ManifestWork OCM resource that delivers manifests to a workload cluster
FleetApp Helm chart install onto a Ready cluster the operator selects
FleetChart Hub library entry for a published OCI chart
FleetAppRoute edge.umkim.com route resource for hub or site ingress
Management site Hub-representing site; it does not host workload clusters
Registry site Operator-created site that can own workload clusters
Detach Default cluster delete mode; removes hub management while keeping spoke K3s and workloads
ingress entry Named site row under spec.edge.ingress[] (port_forward or reverse_proxy)
ingressId Cluster binding to a site ingress entry
hubGateway Site toggle enabling hub-fronted public application URLs
umkim CLI for authenticated fleet operations against the hub API
candidates Capability filter helper for Ready clusters; not a placement engine
nfs_local Single-node local RWX via on-node NFS and nfs-client StorageClass
YAIDAP Yet Another Inventory-Driven Ansible Provisioner — sibling L0 repo for metal/VM provisioning on a site jumphost
TempXE Temporary PXE container used by YAIDAP for bare-metal OS install and PXE hardware discovery
Schedule token Placeholder vm_location value (least-utilized, auto, or empty) resolved to a concrete hypervisor after create_vm
Provision handoff Connector output fragment (ansible_host, hostname, OS family) used for enroll / add-worker
Sync phase Hub inventory push state in _meta/meta.json: pending, dirty, syncing, or synced