-
Notifications
You must be signed in to change notification settings - Fork 60
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
CI: add operator tests job for peer-pods #336
Comments
Hey @wainersm - thanks for raising this. What are your expectations for this work - to create a new job that installed the peer-pod version of cc runtime and check that the kata-remote runtimeClass is available, or add a new test to the existing jobs to do the same thing? |
Hi @stevenhorsman !
I opened this issue thinking on the former: create a new job to run the current operator tests (install, uninstall) with Makes sense? |
Yep - that's what I expected, but just wanted to double-check. Thanks! |
Add the ability to pass through ccruntime overlay config in the e2e test scripts and add matrix to test peer-pods in the cc runtime e2e tests. Fixes: confidential-containers#336 Signed-off-by: stevenhorsman <[email protected]>
@wainersm - FYI I knocked together https://github.com/confidential-containers/operator/compare/main...stevenhorsman:peerpods-tests?expand=1 whilst in a meeting. I'm pretty sure that it's not what you are after, but I thought I'd share to get some feedback |
Scenario 1: Run operator tests for peer-pods on an Ubuntu VM runner
Scenario 2: Run operator tests dailyfor peer-pods on an Ubuntu runner
Use case: As a developer that opens a pull request to this repository, I want to have the operator installed for
config/samples/ccruntime/peer-pods/
and operator tests ran so that I can be assured my changes don't break the peer-pods installation (**)We might want to run a peer-pods simple functional (a.k.a smoke) test as well but I believe this can be tracked in another issue. The scope for this one is only to run the operator tests.
Cc @stevenhorsman
The text was updated successfully, but these errors were encountered: