-
Notifications
You must be signed in to change notification settings - Fork 5.1k
wip: Remove depdendency on crictl for listing containers #22352
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
base: master
Are you sure you want to change the base?
Conversation
…ith annotation-based filtering and dynamic CRIO runtime detection.
…t functions, dynamically for crio and defaulting to runc for containerd/docker.
…lly determining for CRIO and explicitly setting for Docker.
…perations by parsing `crio config`.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: medyagh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/ok-to-test |
| } | ||
|
|
||
| // crioOCIInfo returns the runtime executable (e.g. runc) and its root path by parsing 'crio config' | ||
| func crioOCIInfo(cr CommandRunner) (string, string, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
once we unify the KIC/VM crio configs this step should only be done on None Driver for crio.
|
kvm2 driver with docker runtime DetailsTimes for minikube ingress: 17.4s 16.3s 16.3s 15.8s 15.8s Times for minikube start: 40.9s 40.8s 41.8s 38.3s 38.6s docker driver with docker runtime DetailsTimes for minikube ingress: 10.7s 10.7s 10.7s 12.7s 10.7s Times for minikube start: 19.5s 21.7s 18.8s 19.2s 21.2s docker driver with containerd runtime DetailsTimes for minikube start: 16.7s 20.3s 16.8s 20.5s 19.9s Times for minikube ingress: 23.2s 23.2s 23.2s 23.2s 23.2s |
|
@medyagh: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
Here are the number of top 10 failed tests in each environments with lowest flake rate. Besides the following environments also have failed tests: To see the flake rates of all tests by environment, click here. |
The crictl dependency for listing containers has been removed in favor of direct OCI runtime calls, which provides a more reliable "ground truth" of running containers. as discussed here
#22264