-
Notifications
You must be signed in to change notification settings - Fork 112
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
Document BMO e2e on real hardware #365
Comments
/triage accepted |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
It is still on our wishlist |
@Rozzii: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
The BMO e2e tests have been designed to work also on real hardware. We should check that it actually works, and document how to do it. I think this could fit well in the user-guide, targeted at contributors, but perhaps also as a way for users to check that BMO works with their hardware. A conformance test if you like.
From a high perspective, the process should look something like this:
The text was updated successfully, but these errors were encountered: