Add new cluster profiles: metal-dpf-doca4 and metal-dpf-doca5 (2)

[josecastillolema]

Part 2 of #83086

cc @wabouhamad

Summary by CodeRabbit

• Adds metal-dpf-doca4 and metal-dpf-doca5 cluster profiles to OpenShift CI infrastructure.
• Defines quota-slice lease types and secrets for both external cluster profiles.
• Enables Gitleaks secret checking with version 8.30.0.

[coderabbitai]

Walkthrough

The cluster profile configuration adds the external metal-dpf-doca4 and metal-dpf-doca5 profiles. Each profile includes quota-slice lease settings and a secret reference.

Changes

Cluster profile configuration

Layer / File(s)	Summary
Add DPF cluster profiles ci-operator/step-registry/cluster-profiles/cluster-profiles-config.yaml	Adds the metal-dpf-doca4 and metal-dpf-doca5 external profiles with quota-slice lease types, names, and secrets.

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

Possibly related PRs

• openshift/release#83086: Adds corresponding secrets and Boskos quota-slice configuration for these cluster profiles.

Suggested reviewers: dustman9000, amisstea

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
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 changes only cluster-profiles-config.yaml and adds two static YAML profile entries; it adds no Ginkgo tests or test titles.
Test Structure And Quality	✅ Passed	The PR changes only a cluster-profile YAML file; no Ginkgo test files, It blocks, lifecycle hooks, waits, or assertions are present to review.
Microshift Test Compatibility	✅ Passed	The PR changes only cluster profile YAML; it adds no Ginkgo e2e tests or MicroShift-sensitive test code, so this check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR changes only one YAML configuration file, adding cluster profiles; it adds no Ginkgo e2e tests or multi-node test assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	The patch changes only cluster profile registry entries for two external profiles; it adds no deployment, controller, node-selection, affinity, replica, spread, taint, or PDB scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The commit changes only cluster-profiles-config.yaml and adds no OTE binary or process-level stdout/logging code.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The commit changes only one YAML configuration file with two external cluster profiles; it adds no Ginkgo e2e tests or network connectivity code.
No-Weak-Crypto	✅ Passed	The 8-line patch adds only external cluster-profile metadata and secret references; no weak algorithms, crypto operations, custom crypto, or secret comparisons appear.
Container-Privileges	✅ Passed	The PR changes only cluster profile metadata. Added lines contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The commit only adds two YAML cluster-profile records with profile names, lease types, and secret references; it adds no logging code or passwords, tokens, API keys, PII, hostnames, or customer data.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely identifies the two new cluster profiles added by the pull request.

✨ 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]
@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.

[wabouhamad]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: josecastillolema, Prucek, wabouhamad

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/cluster-profiles/OWNERS [Prucek]

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

[openshift-ci]

@josecastillolema: 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.