Merged
Conversation
1989496 to
e9479ab
Compare
Add integration tests for CRI-O container runtime, similar to the existing Docker integration tests. This includes: - CrioActions interface in the test framework for managing CRI-O containers via crictl CLI - Test cases for container discovery by ID and name, basic container stats, CPU stats, and memory stats - Build scripts for running CRI-O tests locally and in Docker - GitHub Actions workflow job for CI The CRI-O tests use the pod sandbox model required by CRI-O, where containers run inside pods. The test harness handles pod lifecycle management and cleanup automatically. Signed-off-by: Davanum Srinivas <davanum@gmail.com>
d2b8956 to
81cb31a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add integration tests for CRI-O container runtime, similar to the existing Docker integration tests. This includes:
The CRI-O tests use the pod sandbox model required by CRI-O, where containers run inside pods. The test harness handles pod lifecycle management and cleanup automatically.