ci: tls-scanner informing on 4.22 and 5.0 payload#79758
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
✅ Files skipped from review due to trivial changes (2)
🚧 Files skipped from review as they are similar to previous changes (5)
WalkthroughRegisters a TLS scanner image, schedules yearly ChangesTLS Scanner Integration for OpenShift releases
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested labels
Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
bf162ad to
ad4e440
Compare
ad4e440 to
8ca9bbc
Compare
|
/lgtm |
|
/pj-rehearse auto-ack |
|
@smith-xyz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
This should be good. worth a rerun though. |
|
@richardsonnick: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse abort |
|
@smith-xyz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-tls-scan |
|
@smith-xyz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@richardsonnick see the error here - let me try to set this to cli instead |
8ca9bbc to
e6928a7
Compare
|
/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-tls-scan |
|
@smith-xyz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
e6928a7 to
e3c509e
Compare
|
[REHEARSALNOTIFIER]
A total of 632 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-tls-scan |
|
@smith-xyz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-tls-scan |
|
@smith-xyz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@smith-xyz: The following test failed, say
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 |
|
/pj-rehearse ack |
|
@smith-xyz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jupierce, richardsonnick, smith-xyz 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 |
Adds tls scanner as informing on 4.22 and 5.0 ocp payload
Summary by CodeRabbit
This PR wires the TLS scanner into OpenShift nightly release pipelines for 4.22 and 5.0 as an informing (non-blocking) payload check, and adds matching disabled/optional private verify entries.
What changed in practical terms
@yearly) that runs the tls-scanner-run test on the openshift-org-aws cluster profile using the ipi-aws workflow and sets compute resources (COMPUTE_NODE_TYPE m5.2xlarge as configured in job metadata).Practical impact
Files touched (high level)
Notes from PR discussion