Skip to content

Conversation

saschagrunert
Copy link
Member

What type of PR is this?

/kind feature

What this PR does / why we need it:

Use the new conmon-rs API to pre-validate the version requirements.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

Early pre-validate the configured pod runtime (`conmon-rs`) on config validation.

@saschagrunert saschagrunert requested a review from mrunalp as a code owner July 8, 2025 08:54
@openshift-ci openshift-ci bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Jul 8, 2025
@openshift-ci openshift-ci bot requested review from klihub and littlejawa July 8, 2025 08:55
Copy link
Contributor

openshift-ci bot commented Jul 8, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 8, 2025
@saschagrunert saschagrunert force-pushed the conmonrs-version branch 3 times, most recently from d53ee48 to 20f7796 Compare July 9, 2025 10:30
@saschagrunert saschagrunert changed the title WIP: Pre-check conmon-rs version on config validation Pre-check conmon-rs version on config validation Jul 9, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 9, 2025
@saschagrunert saschagrunert changed the title Pre-check conmon-rs version on config validation Pre-check streaming websockets on config validation Jul 9, 2025
Copy link

codecov bot commented Jul 9, 2025

Codecov Report

Attention: Patch coverage is 84.61538% with 6 lines in your changes missing coverage. Please review.

Project coverage is 66.88%. Comparing base (5e12be1) to head (898a9d0).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #9324      +/-   ##
==========================================
- Coverage   66.91%   66.88%   -0.04%     
==========================================
  Files         198      198              
  Lines       27406    27426      +20     
==========================================
+ Hits        18340    18345       +5     
- Misses       7551     7563      +12     
- Partials     1515     1518       +3     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

This change disallows streaming websockets for other runtimes than
"pod". If conmon-rs version API is available, then it will also print
the version. If the version API is not available, then the config
validation implicitly assumes that conmon-rs < 0.7.0 is being used,
which does not support the streaming server at all.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
@saschagrunert
Copy link
Member Author

@cri-o/cri-o-maintainers PTAL

@cri-o cri-o deleted a comment from openshift-ci bot Jul 9, 2025
@cri-o cri-o deleted a comment from openshift-ci bot Jul 9, 2025
@haircommander
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 9, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit c926682 into cri-o:main Jul 9, 2025
126 of 131 checks passed
@saschagrunert saschagrunert deleted the conmonrs-version branch July 10, 2025 06:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants