rant
It's utterly ridiculous how complicated it is to get cri-o and Kubernetes to work on Fedora CoreOS.
Everything is supposed to be layered on top of the base OS but that speaks against the idea of image-based systems.
OpenShift solved this issue by… using a custom build of cri-o, Kubernetes and Fedora CoreOS, that uses these components from outside the distro.
And I'm sitting here, fiddling around and probably built a custom OS as well, just because there seems to be no way around it. :/
rant
After an evening of fighting with osbuild and osbuild-composer, which is already much easier than coreos-assembler, and some fights with Fedora modularity, and a whole new way to define RPM repositories and their keys, I managed to build an insecure ostree image. Progress!
Maybe at the end of the weekend I'll manage to setup a functioning install and move my infrastructure to it. Or it all ends up horrible and I'll throw stuff into the bin. Who knows… 🤷
rant / calmed
After quite some annoyance, I wrote various parts of it down, which might becomes an own blog article, for now it's a README in my new os directory:
https://git.shivering-isles.com/shivering-isles/infrastructure-gitops/-/blob/bbb7fb958c699b64d73e6fa4d5e29d9c2d37c62e/os/README.md
First tests make it look quite okay. Some further tweaks required, but it's on a good way.