-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide builds with libvirt support #1213
Comments
This is an existing release issue, not an installer issue. /close |
@wking: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'm not sure why this issue shoul dbe a dupe of the linked bug. Thanks AI
...
|
The installer team doesn't build update-payloads, we just pin what ART pushes to quay.io. Until they push the libvirt machine-API image too (the linked issue), pinned installer releases will have issues on libvirt with quay.io payloads. There's a separate issue of "once ART fixes the update payloads, will released installer binaries include libvirt support". That's wont-fix, because libvirt is dev-only best-effort (more in #955). But it's easy to work around, just check out the released tag and build yourself with |
KubeVirt plans ot be running on Origin 4. In order to do so we need to setup an OCP 4 environment, the installer looks like the right way to set it up.
Please provide installer builds with libvirt support in order to avoid that we have to perform those builds in our CI.
The text was updated successfully, but these errors were encountered: