(Claude, prompted by Sebastian)
Found while modeling OS as a PICT dimension for the e2e test matrix — Rocky isn't actually wired into the k8s-install path today, just used for a narrower packaging test. Three layers are missing, in order of what would need to land first:
-
No install-script support for anything but Ubuntu. installer/internal/algo/ only has ubuntu-templates/ (install.sh.tmpl/uninstall.sh.tmpl, apt-based). installer/registry.go's GetSupportedRegistry() only registers Ubuntu 20.04/22.04/24.04 (x86-64 + arm64) -- the code has literal /* PLACEHOLDER - ADD MORE OS HERE */ and /* PLACEHOLDER - POINT MORE DISTRO VERSIONS */ comments marking the extension points, but nothing fills them in for a yum/dnf-based distro.
-
No OCI bundle for Rocky. K8s components (kubeadm/kubelet/etc.) are distributed as OCI bundles per (OS, k8s-version) pair from quay.io/platform9. Only Ubuntu bundles are confirmed to exist there, and installer/bundle_builder/config/ (which builds them) only has ubuntu/20_04/k8s/1_22 -- no Rocky/RHEL config to build from even locally.
-
No join-capable e2e image for Rocky. test/e2e/packaging/RockyDockerFile -> byoh/packaging-test-rocky:dev exists, but only to prove the .deb/.rpm package installs/uninstalls cleanly -- not to actually join a cluster as a node. Unverified whether it has what the join flow needs (kernel modules, systemd units, CNI tooling); likely doesn't, since that was never its purpose.
Steps 1 and 2 are installer/product work, not test-infra -- a new e2e image alone (step 3) can't make Rocky a real test target without them.
(Claude, prompted by Sebastian)
Found while modeling
OSas a PICT dimension for the e2e test matrix — Rocky isn't actually wired into the k8s-install path today, just used for a narrower packaging test. Three layers are missing, in order of what would need to land first:No install-script support for anything but Ubuntu.
installer/internal/algo/only hasubuntu-templates/(install.sh.tmpl/uninstall.sh.tmpl, apt-based).installer/registry.go'sGetSupportedRegistry()only registers Ubuntu 20.04/22.04/24.04 (x86-64 + arm64) -- the code has literal/* PLACEHOLDER - ADD MORE OS HERE */and/* PLACEHOLDER - POINT MORE DISTRO VERSIONS */comments marking the extension points, but nothing fills them in for a yum/dnf-based distro.No OCI bundle for Rocky. K8s components (kubeadm/kubelet/etc.) are distributed as OCI bundles per (OS, k8s-version) pair from
quay.io/platform9. Only Ubuntu bundles are confirmed to exist there, andinstaller/bundle_builder/config/(which builds them) only hasubuntu/20_04/k8s/1_22-- no Rocky/RHEL config to build from even locally.No join-capable e2e image for Rocky.
test/e2e/packaging/RockyDockerFile->byoh/packaging-test-rocky:devexists, but only to prove the.deb/.rpmpackage installs/uninstalls cleanly -- not to actually join a cluster as a node. Unverified whether it has what the join flow needs (kernel modules, systemd units, CNI tooling); likely doesn't, since that was never its purpose.Steps 1 and 2 are installer/product work, not test-infra -- a new e2e image alone (step 3) can't make Rocky a real test target without them.