DPF: Add scale target

[josecastillolema]

Adds a /test scale target that runs node-density-cni with 30 pods per node. If P99 pod creation latency is higher than 60 secs the job will report failure.

Summary by CodeRabbit

Adds an optional /test scale job to the OpenShift DPF CI pipelines for main and release-4.22. The job runs the node-density-cni workload with 30 pods per node on DPU workers and fails when P99 pod creation latency exceeds 60 seconds. It also enables secret scanning with Gitleaks 8.30.0.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 3fe25b65-f8de-4921-87d5-a91c0e7bc5f4

📥 Commits

Reviewing files that changed from the base of the PR and between b5f6060 and bc79e4a.

⛔ Files ignored due to path filters (2)

• ci-operator/jobs/rh-ecosystem-edge/openshift-dpf/rh-ecosystem-edge-openshift-dpf-main-presubmits.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/rh-ecosystem-edge/openshift-dpf/rh-ecosystem-edge-openshift-dpf-release-4.22-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (2)

• ci-operator/config/rh-ecosystem-edge/openshift-dpf/rh-ecosystem-edge-openshift-dpf-main.yaml
• ci-operator/config/rh-ecosystem-edge/openshift-dpf/rh-ecosystem-edge-openshift-dpf-release-4.22.yaml

✨ 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-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: josecastillolema

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/config/rh-ecosystem-edge/openshift-dpf/OWNERS [josecastillolema]
• ci-operator/jobs/rh-ecosystem-edge/openshift-dpf/OWNERS [josecastillolema]

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@josecastillolema: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.
The following jobs are not rehearsable without the network-access-rehearsals-ok, and approved labels present on this PR. This is due to the restrict_network_access field being set to false. The network-access-rehearsals-ok label can be added by any openshift org member other than the PR's author by commenting: /pj-rehearse network-access-allowed:

Test name
pull-ci-rh-ecosystem-edge-openshift-dpf-main-scale
pull-ci-rh-ecosystem-edge-openshift-dpf-release-4.22-scale

[enothen]

/pj-rehearse network-access-allowed

[openshift-merge-bot]

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

[josecastillolema]

/pj-rehearse pull-ci-rh-ecosystem-edge-openshift-dpf-main-scale

[openshift-merge-bot]

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

[openshift-ci]

@josecastillolema: The following test 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/rehearse/rh-ecosystem-edge/openshift-dpf/main/scale	bc79e4a	link	unknown	/pj-rehearse pull-ci-rh-ecosystem-edge-openshift-dpf-main-scale

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.