Skip to content
This repository was archived by the owner on Feb 1, 2026. It is now read-only.

Conversation

@mythi
Copy link
Contributor

@mythi mythi commented Aug 5, 2025

kata-deploy supports Ubuntu 24.04 (and 25.04) based TDX enablement. Since the operator e2e does not test any TEE specifics, it's enough to test that kata-qemu-tdx runtimeclass gets created on a vanilla Ubuntu 24.04.

kata-deploy supports Ubuntu 24.04 (and 25.04) based TDX
enablement. Since the operator e2e does not test any TEE
specifics, it's enough to test that kata-qemu-tdx runtimeclass
gets created on a vanilla Ubuntu 24.04.

Signed-off-by: Mikko Ylinen <[email protected]>
@mythi mythi requested a review from a team as a code owner August 5, 2025 12:15
@mythi
Copy link
Contributor Author

mythi commented Aug 5, 2025

It seems this cannot be tested because of ccruntime-pr.yaml.

@mythi
Copy link
Contributor Author

mythi commented Aug 8, 2025

It seems this cannot be tested because of ccruntime-pr.yaml.

one option is to just get it merged and see the nightly results. @confidential-containers/operator-maintainers WDYT?

@stevenhorsman
Copy link
Member

I think this is fine for now, but we discussed the idea of doing use cases scenarios in the operator e2e testing a long time ago to add more tests and the standard runner wouldn't work for that. However I'm not sure anyone has bandwidth/plans to add this testing, so maybe it's a problem for a future day?

@mythi
Copy link
Contributor Author

mythi commented Aug 11, 2025

Right, I believe #446 was one of those e2e use cases. I closed it last week since I don't think it's going to get finished and it's been on hold for about a year now.

If TEE based tests are added, I can revisit this change but as it is now, we won't loose any coverage for TDX.

Copy link
Member

@stevenhorsman stevenhorsman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable to me based on our current e2e test coverage

@mythi
Copy link
Contributor Author

mythi commented Aug 13, 2025

@ldoktor mind checking this?

Copy link
Contributor

@ldoktor ldoktor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me and should work as long as we don't introduce functional test.

I like the instance/exclude removal replaced with include only. We should do that for sev-snp as well (only the exclude part, not the change of the instance type itself)

@mythi mythi merged commit 9e7a37d into confidential-containers:main Aug 13, 2025
28 of 30 checks passed
@mythi
Copy link
Contributor Author

mythi commented Aug 13, 2025

will monitor nightly-e2e results for tdx and act if needed.

@ldoktor
Copy link
Contributor

ldoktor commented Aug 13, 2025

Sure, hopefully it'll work well. I was running local testing and it failed, but could have been just timeout issue. I'll try again.

@ldoktor
Copy link
Contributor

ldoktor commented Aug 13, 2025

Cool, the second run worked well (on my ubuntu vm)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants