-
Notifications
You must be signed in to change notification settings - Fork 85
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: run e2e tests for libvirt with CRI-O #2068
base: main
Are you sure you want to change the base?
Commits on Oct 8, 2024
-
versions: bump version of kcli
In order to use kcli to create a k8s cluster with configured with cri-o, it will be needed to use a version newer than 07/02/2024 which containers the karmab/kcli@77cf2cb fix. So picking the latest version available at the time of this commit. Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 398d959 - Browse repository at this point
Copy the full SHA 398d959View commit details -
libvirt/kcli_cluster.sh: add support to CRI-O
By exporting the CONTAINER_RUNTIME=crio variable, kcli will create a k8s cluster configured CRI-O: $ export CONTAINER_RUNTIME=crio $ ./src/cloud-api-adaptor/libvirt/kcli_cluster.sh create Fixes confidential-containers#1981 Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for c179d8c - Browse repository at this point
Copy the full SHA c179d8cView commit details -
test/e2e: new container_runtime property for libvirt
Commit a0247ae introduced a new parameter (CONTAINER_RUNTIME) for docker provider, allowing users to specify the container runtime used. Some tests will take decisions based on that property, for example, whether nydus snapshotter messages should be inspected or not. Likewise, this added the handler for that property for libvirt, so allowing to test with cri-o too. Fixes confidential-containers#1981 Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for dc89125 - Browse repository at this point
Copy the full SHA dc89125View commit details -
workflows/libvirt: add e2e job to test with CRI-O
Added a new container_runtime matrix column to generate one job for each runtime: containerd and crio. Fixes confidential-containers#1981 Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 8a12b1a - Browse repository at this point
Copy the full SHA 8a12b1aView commit details -
workflows/libvirt: allow the e2e crio job to fail
Let's keep it running for a while on CI, once it's stable we can remove the continue-on-error. Fixes confidential-containers#1981 Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 0931173 - Browse repository at this point
Copy the full SHA 0931173View commit details -
test/e2e: adapt DoTestRestrictivePolicyBlocksExec for CRI-O
The DoTestRestrictivePolicyBlocksExec test for CRI-O will have the "error executing command in container" error message instead of "failed to exec in container". So adjusted the expected strings on the error message to consider the output of CRI-O too. Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 1687ba8 - Browse repository at this point
Copy the full SHA 1687ba8View commit details -
test/e2e: skip libvirt tests for CRI-O
These test are already skipped on CI, also disabled them when running locally because they fail. Related-to: confidential-containers#2100 Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 711ee01 - Browse repository at this point
Copy the full SHA 711ee01View commit details