Skip to content
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

Closed
fabiand opened this issue Feb 8, 2019 · 4 comments
Closed

Provide builds with libvirt support #1213

fabiand opened this issue Feb 8, 2019 · 4 comments

Comments

@fabiand
Copy link

fabiand commented Feb 8, 2019

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.

@wking
Copy link
Member

wking commented Feb 8, 2019

This is an existing release issue, not an installer issue.

/close

@openshift-ci-robot
Copy link
Contributor

@wking: Closing this issue.

In response to this:

This is an existing release issue, not an installer issue.

/close

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.

@fabiand
Copy link
Author

fabiand commented Feb 8, 2019 via email

@wking
Copy link
Member

wking commented Feb 8, 2019

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 TAGS=libvirt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants