-
Notifications
You must be signed in to change notification settings - Fork 120
CNF-15505: Remove container runtime selection #1219
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
CNF-15505: Remove container runtime selection #1219
Conversation
|
Skipping CI for Draft Pull Request. |
58b8352 to
1b1e182
Compare
|
/test all |
1b1e182 to
a529fc7
Compare
|
/test all |
1 similar comment
|
/test all |
95eaf2c to
75c64c0
Compare
|
/test all |
75c64c0 to
f562028
Compare
|
/test all |
f562028 to
0063564
Compare
|
/test all |
|
@rbaturov: This pull request references CNF-15505 which is a valid jira issue. DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@rbaturov: No Jira issue is referenced in the title of this pull request. DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
A new patch has been introduced for CRI-O, allowing the container runtime for the high-performance runtime class to be inherited from the system instead of being detected and explicitly set. cri-o/cri-o#8753 As a result, the controller no longer needs to identify the container runtime from the containerRuntimeConfig for setting it in the 99-runtimes.conf snippet. Signed-off-by: Ronny Baturov <[email protected]>
0063564 to
de20252
Compare
|
/retest-required |
ffromani
left a comment
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.
need to review the e2e test, and there are pending comments open.
Besides that, I'd like a clarification about a test utility.
The logic per se LGTM
test/e2e/performanceprofile/functests/utils/cgroup/runtime/runtime.go
Outdated
Show resolved
Hide resolved
The GetContainerRuntimeTypeFor function has been updated to provide more accurate output regarding the runtime class used on the node. Previously, it relied on reading the runtime path from the CRI-O configuration file, but this is no longer viable, as the runtime path is no longer written to the file. The new approach directly checks the container process on the node using the ps tool to determine the runtime in use. The new command outputs the conmon process of the container and greps the container runtime from the -r argument using regex. For example: /bin/ps aux | grep 'tuned-ncp4j' root 6317 0.0 0.0 8312 1600 ? Ss 12:25 0:00 /usr/bin/conmon -b /run/containers/storage/overlay-containers/f492c7c342b71.../userdata/conmon-pidfile -p /run/containers/storage/overlay-containers/f492c7c342b71e19e.../userdata/pidfile --persist-dir /var/lib/containers/storage/overlay-containers/f492c7c342b7..../userdata -r /usr/bin/crun --runtime-arg --root=/run/crun --socket-dir-path /var/run/crio --syslog -u f492c7c3... -s root 90775 0.0 0.0 3332 1600 ? S+ 13:57 0:00 grep tuned-ncp4j Signed-off-by: Ronny Baturov <[email protected]>
When we have no ContainerRuntimeConfig in the system, the high-performance class should use the runtime that is currently being used in the system. This should be crun for 4.18 systems, or runc if upgraded from older version and not explicitly switched to crun. Since the selected runtime is not directly exposed, we target the tuned pod to determine which runtime is handling it, using this as an indicator for the node's default runtime. Moreover, instead of checking the container runtime for the high-performance pods from the conf file (which no longer is possible), we will create a test pod and check the container runtime used in practice. Signed-off-by: Ronny Baturov <[email protected]>
e86d851 to
dec1553
Compare
|
/retest-required |
2 similar comments
|
/retest-required |
|
/retest-required |
|
/retest-required |
ffromani
left a comment
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.
my comments are addressed, LGTM pending review of the e2e tests
|
/retest-required |
@mrniranjan Has reviewed. |
|
LGTM from my side |
|
/retest-required |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rbaturov, yanirq 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 |
|
/test e2e-pao-updating-profile-hypershift |
|
@rbaturov: all tests passed! Full PR test history. Your PR dashboard. 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. |
|
/lgtm |
|
@rbaturov: cannot checkout DetailsIn response to this:
Instructions 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. |
|
@rbaturov: #1219 failed to apply on top of branch "release-4.17": DetailsIn response to this:
Instructions 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. |
|
/cherry-pick release-4.18 |
|
@rbaturov: new pull request created: #1233 DetailsIn response to this:
Instructions 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. |
|
[ART PR BUILD NOTIFIER] Distgit: cluster-node-tuning-operator |
A new patch has been introduced for CRI-O, allowing the container runtime for the high-performance runtime class to be inherited from the system instead of being detected and explicitly set. cri-o/cri-o#8753
As a result, the controller no longer needs to identify the container runtime from the containerRuntimeConfig for setting it in the 99-runtimes.conf snippet.
This PR encompasses all (need to verify) required changes.