Scenario 1: Run operator tests on an AMD SEV-SNP runner
Scenario 2: Run operator tests daily on an AMD SEV-SNP 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-SNP 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. Also we do have plans to use the k8s' node feature discovery (see Detect confidential computing capabilities of the cluster node)
Scenario 1: Run operator tests on an AMD SEV-SNP runner Scenario 2: Run operator tests daily on an AMD SEV-SNP 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-SNP 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. Also we do have plans to use the k8s' node feature discovery (see Detect confidential computing capabilities of the cluster node)
Related-to: CI: add operator tests job for SEV
Cc @ryansavino @fitzthum