You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tests: switch to custom FCOS image with CRI-O via coreos-assembler
Build a custom FCOS qcow2 with CRI-O and Kubernetes packages baked in
using coreos-assembler. This replaces the vanilla FCOS + containerd
approach, eliminating the SELinux permissive workaround (CRI-O has
native SELinux support and properly labels privileged containers).
The test VM image build is now a multi-stage Containerfile:
1. Build a bootable container (FROM fcos, add K8s + CRI-O repos, dnf
install) via inner podman build
2. Use cosa import + cosa osbuild qemu to produce the qcow2
3. Copy the qcow2 into the final test harness image
The config.bu is simplified: no more K8s binary downloads, containerd
config, CNI plugins install, or SELinux permissive hack.
Also fix daemon DaemonSet ServiceAccount name mismatch with kustomize
namePrefix by making it configurable via DAEMON_SERVICE_ACCOUNT env
var, and removing the operator-managed ServiceAccount (now deployed by
kustomize). Fix DAEMON_SERVICE_ACCOUNT substitution in build-installer.
Assisted-by: OpenCode (Claude Opus 4.6)
0 commit comments