Prerequisites

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

UMKIM v0.1.0 is experimental and unsupported. Prepare an isolated evaluation environment; do not infer production support from the production profile.

Hub and operator host

Use a Rocky Linux 9 hub host with a non-root operator account and passwordless sudo, plus enough CPU, memory, and disk for K3s, Harbor, and image builds. If public edge routing is enabled, review the required WAN ports in Security and ports before exposing any service.

Prepare the tagged checkout

Harbor fleet image builds expect sibling checkouts beside the UMKIM tree:

sudo dnf install -y ansible-core git python3-pip python3-libselinux \
  httpd-tools podman containernetworking-plugins
pip install netaddr

# HTTPS (or matching git@github.com:rborso/... SSH URLs for every clone)
git clone https://github.com/rborso/umkim.git <workspace>/umkim
cd <workspace>/umkim
git checkout v0.1.0
ansible-galaxy collection install -r requirements.yml

cd <workspace>
git clone https://github.com/rborso/control-plane.git
git clone https://github.com/rborso/fleet-olm-subscription-sp.git
git clone https://github.com/rborso/fleet-helm-release-sp.git
git clone https://github.com/rborso/k8s-container-service-provider.git
git clone https://github.com/rborso/kubevirt-service-provider.git

Use one transport (HTTPS or SSH) for every clone. Then pin and verify siblings from the release pin file rather than copied commit IDs:

cd <workspace>/umkim
./scripts/fleet-checkout-pins.sh
./scripts/fleet-verify-pins.sh --strict
./scripts/bootstrap-hub-inventory.sh

Required beside umkim:

control-plane
fleet-olm-subscription-sp
fleet-helm-release-sp
k8s-container-service-provider
kubevirt-service-provider

See also Related repositories. The optional umkim-catalog checkout supplies additional catalog content only; it is not required for hub installation or the FCJ lifecycle.

The authoritative pin file is inventory/group_vars/all/fleet_git_pins.yml, copied by inventory bootstrap.

Before install

Complete the generated inventory with your own host, network, DNS, and vault values. Configure public DNS only when you deliberately enable public fleet-edge routing. Continue with Install the hub.