Related repositories
UMKIM v0.2 hub images are built from the umkim checkout only. Sibling service-provider repositories are not required for hub install, cluster join, or fleet image builds.
| Repository | Role in v0.2 |
|---|---|
| umkim | Ansible fleet, controllers, console, and hub image builds |
| yaidap | Optional L0 metal/VM provisioner for sites with spec.provision.provider=yaidap (not required for hub install or greenfield cluster join) |
Historical v0.1 siblings (not required in v0.2)
Section titled “Historical v0.1 siblings (not required in v0.2)”These repositories were required for v0.1.0 DCM catalog and provider paths. They are not part of the v0.2 operator model:
| Repository | Former role |
|---|---|
| control-plane | DCM control plane (removed) |
| fleet-olm-subscription-sp | OLM subscription provider (removed) |
| fleet-helm-release-sp | Helm release provider (removed) |
| k8s-container-service-provider | Container provider (removed) |
| kubevirt-service-provider | KubeVirt provider (removed) |
| umkim-catalog | Optional catalog content (removed from v0.2 path) |
For v0.1.0 documentation that still references these repositories, see the 0.1.0 docs.
Use VERSIONS.md and examples/inventory/hub-only/group_vars/all/common.yml for component version pins.
Before publishing a release, verify that the canonical GitHub repository is publicly visible to the intended audience.