Skip to content

Conversation

@Vincent056
Copy link

The cel-scanner reads collected resources and evaluates them against the defined CEL rules.
The scanner pod creates Compliance Check Results directly
The results are saved in a specified directory on the pod as optional.

…eferences

- Introduce scannerType to ComplianceScan and ComplianceSuite for specifying OpenSCAP or CEL.
- Add custom rule CRD (compliance.openshift.io_customrules.yaml) and types.
- Extend TailoredProfile references with a 'kind' field to differentiate between Rule and CustomRule.
The cel-scanner reads collected resources and evaluates them against the defined CEL rules.
The scanner pod creates Compliance Check Result directly
The results are saved in a specified directory on the pod as optional.
@Vincent056
Copy link
Author

#686 needs to be merged before this PR, we cherry picked the commit from that PR

@openshift-ci-robot
Copy link
Collaborator

@Vincent056: This pull request references CMP-2872 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

The cel-scanner reads collected resources and evaluates them against the defined CEL rules.
The scanner pod creates Compliance Check Results directly
The results are saved in a specified directory on the pod as optional.

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.

@openshift-ci openshift-ci bot requested review from xiaojiey and yuumasato February 25, 2025 11:08
@openshift-ci
Copy link

openshift-ci bot commented Feb 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Vincent056

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

The pull request process is described here

Details 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

@rhmdnd rhmdnd added the CEL CEL features and functionality label Feb 27, 2025
@openshift-ci
Copy link

openshift-ci bot commented Feb 28, 2025

@Vincent056: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/verify 1245440 link true /test verify
ci/prow/unit 1245440 link true /test unit
ci/prow/images 1245440 link true /test images
ci/prow/e2e-aws-serial 1245440 link true /test e2e-aws-serial
ci/prow/e2e-rosa 1245440 link true /test e2e-rosa
ci/prow/e2e-aws-parallel 1245440 link true /test e2e-aws-parallel
ci/prow/e2e-aws-parallel-arm 1245440 link true /test e2e-aws-parallel-arm
ci/prow/e2e-aws-serial-arm 1245440 link true /test e2e-aws-serial-arm

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@Vincent056
Copy link
Author

close in favor of #671

@Vincent056 Vincent056 closed this Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved CEL CEL features and functionality jira/valid-reference

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants