CRI-O is coupled to Kubernetes for the releases, while the major and the minor follows Kubernetes streams, the patch version is independant, so we need to fetch the latest patch release for each minor Kubernetes version.
sysupdate configuration is generated similar to Kubernetes.
Locally tested, will trigger a release right after to generate cri-o missing images.
CRI-O is coupled to Kubernetes for the releases, while the major and the minor follows Kubernetes streams, the patch version is independant, so we need to fetch the latest patch release for each minor Kubernetes version.
sysupdate configuration is generated similar to Kubernetes.
Locally tested, will trigger a release right after to generate cri-o missing images.
Related to: https://github.com/flatcar/sysext-bakery/issues/42