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
Scenario 1: Run operator tests on an AMD SEV runner Scenario 2: Run operator tests daily on an AMD SEV runner
Use case: As a developer that opens a pull request to this repository, I want to have the operator tests executed on AMD SEV so that I can be assured my changes don't the operator on that platform (**)
Scenario 1: Run operator tests on an AMD SEV runner
Scenario 2: Run operator tests daily on an AMD SEV runner
Use case: As a developer that opens a pull request to this repository, I want to have the operator tests executed on AMD SEV so that I can be assured my changes don't the operator on that platform (**)
(**) Although the operator tests don't currently check hardware-specific features, it seems a good idea to run them regardless because they will likely to end up the runners of the smoke tests (see Add simple functional test for SEV). Also we do have plans to use the k8s' node feature discovery (see Detect confidential computing capabilities of the cluster node)
Cc @ryansavino @fitzthum
The text was updated successfully, but these errors were encountered: