NO-JIRA: fix: add nested_podman:true annotation in cryptoscan ref

[fracappa]

Summary by CodeRabbit

• Enables nested Podman for the MicroShift rebase crypto-scan step.
• This allows the OpenShift CI job to run crypto scanning in a nested Podman environment.

[openshift-ci-robot]

@fracappa: This pull request explicitly references no jira issue.

Details

In 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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: f6164a6c-5b62-422f-87f1-cf28b5221c16

📥 Commits

Reviewing files that changed from the base of the PR and between f85f4e1 and 343c0ae.

📒 Files selected for processing (1)

• ci-operator/step-registry/openshift/microshift/rebase/cryptoscan/openshift-microshift-rebase-cryptoscan-ref.yaml

---

Walkthrough

The MicroShift rebase cryptoscan step now enables nested Podman execution through its step configuration.

Changes

MicroShift cryptoscan configuration

Layer / File(s)	Summary
Nested Podman configuration ci-operator/step-registry/openshift/microshift/rebase/cryptoscan/openshift-microshift-rebase-cryptoscan-ref.yaml	The cryptoscan step sets nested_podman: true.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• openshift/release#82024: Enables nested Podman in the existing MicroShift rebase cryptoscan step.
• openshift/release#83025: Enables nested Podman for a related MicroShift rebase cryptoscan configuration.
• openshift/release#83037: Updates the same cryptoscan step with rootless Podman runtime setup.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the main change: adding the nested_podman:true annotation to the cryptoscan reference.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The patch only adds the static YAML field nested_podman: true; it introduces no Ginkgo tests or dynamic test titles.
Test Structure And Quality	✅ Passed	The pull request changes only one YAML reference by adding nested_podman: true; it adds no Ginkgo tests or cluster operations to review.
Microshift Test Compatibility	✅ Passed	The commit adds only nested_podman: true to a YAML step reference; it adds no Ginkgo tests, APIs, resources, namespaces, or MicroShift assumptions.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The commit changes only one YAML declaration by adding nested_podman: true; it adds no Ginkgo e2e tests or multi-node assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	The changed file is a CI step reference. Its only scheduling-relevant change is nested_podman: true; it adds no replicas, affinity, spread constraints, selectors, tolerations, or PDBs.
Ote Binary Stdout Contract	✅ Passed	The PR adds only nested_podman: true to a YAML step reference; it changes no OTE binary or process-level stdout code.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The pull request adds only nested_podman: true to a YAML step reference and adds no Ginkgo tests or network operations.
No-Weak-Crypto	✅ Passed	The PR adds only nested_podman: true; it introduces no weak algorithm, custom crypto, or secret comparison.
Container-Privileges	✅ Passed	The only PR change is nested_podman: true; the affected reference has none of the listed privilege fields, and its image definition switches to USER 1000.
No-Sensitive-Data-In-Logs	✅ Passed	The PR changes only a YAML annotation, nested_podman: true; it adds no logging or secret-bearing output, and the command script is unchanged.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@fracappa: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-microshift-main-test-rebase	openshift/microshift	presubmit	Registry content changed
pull-ci-openshift-microshift-release-5.0-test-rebase	openshift/microshift	presubmit	Registry content changed
periodic-ci-openshift-microshift-release-5.1-periodics-rebase-on-nightlies	N/A	periodic	Registry content changed
periodic-ci-openshift-microshift-release-5.0-periodics-rebase-on-nightlies	N/A	periodic	Registry content changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@fracappa: all tests passed!

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.

[pacevedom]

/lgtm

[pacevedom]

/pj-rehearse ack

[openshift-merge-bot]

@pacevedom: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fracappa, pacevedom

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:

• ci-operator/step-registry/openshift/microshift/rebase/cryptoscan/OWNERS [fracappa,pacevedom]

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