Skip to content

ci-config: add tls-scanner-run to fips-payload-scan for nightly-4.22 #79624

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.

Sign up for GitHub

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

Closed
redhat-chai-bot wants to merge 1 commit into from
Closed

ci-config: add tls-scanner-run to fips-payload-scan for nightly-4.22 #79624

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions ci-operator/config/openshift/release/openshift-release-main__nightly-4.22.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,10 @@ base_images:
name: tests-private
namespace: ci
tag: "4.22"
tls-scanner-tool:
name: tls-scanner
namespace: tls-scanner
tag: tls-scanner-tool
Comment on lines +90 to +93

@coderabbitai coderabbitai Bot May 21, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Run and commit downstream CI artifact regeneration for this structural config change.

This PR adds a new base image and a new test ref, which are structural ci-operator/config changes. Please run make update and include any resulting generated artifact updates (or confirm it is a true no-op with evidence).

As per coding guidelines: “After modifying CI configuration files in ci-operator/config/, regenerate downstream artifacts by running make update”.

Also applies to: 2430-2430

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/release/openshift-release-main__nightly-4.22.yaml`
around lines 90 - 93, You added a structural CI config entry (tls-scanner-tool
with name: tls-scanner, namespace: tls-scanner, tag: tls-scanner-tool) under
ci-operator/config; run the downstream artifact regeneration by executing make
update, review changes produced (e.g., generated files under the release/ or
ci-operator/jobs/ dirs), and commit those generated files alongside your config
change — if make update produces no changes, include the make output as evidence
in the PR to confirm it is a true no-op.

upi-installer:
name: "4.22"
namespace: ocp
Expand Down Expand Up @@ -2423,6 +2427,7 @@ tests:
test:
- ref: fips-check-node-scan
- ref: fips-check-art-fips
- ref: tls-scanner-run
workflow: ipi-aws
- as: e2e-external-aws
cron: '@weekly'
Expand Down