Merge master to stable new

[nsingla]

Description of your changes:

Checklist:

• You have signed off your commits
• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch master

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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 and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign humairak for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[github-actions]

🚦 Integration Test Verification Required

This pull request is merging main → stable and requires integration test verification.

✅ Required Action:

Comment /integration-tests-ok on this PR only after running the integration tests.

📝 Steps:

1. Run integration tests in OpenShift cluster with latest ODH nightly
   1. Go to this Jenkins job
   2. Provide Cluster Name
   3. Check Install_Cluster checkbox
   4. Check "DEPROVISION_AFTER_INSTALL_FAILURE" if you want to destroy the cluster on job failure automatically
   5. Check "ADD_ICSP" is not checked
   6. Enter ODS_BUILD_URL=odh-nightly
   7. Enter UPDATE_CHANNEL=odh-nightlies
   8. Uncheck RUN_TESTS
   9. Enter RUN_DASHBOARD_TESTS=SmokeSet1 (this will run cypress Dashboard Tests Job as a downstream job)
   10. Run the job
   11. Once the deployment is DONE and your cluster is available, and you have updates in master after the ODH nightly build time:
       • Login to openshift console
       • Go to Operator > Installed Operators > Open Data Hub Operator > Data Science Cluster > default-dsc
       • Open the yaml spec
       • Update the aipipelines section with:

         aipipelines:
              devFlags:
                  manifests:
                    - uri: https://github.com/opendatahub-io/data-science-pipelines-operator/tarball/main
                      contextDir: config
                      sourcePath: base
              managementState: Managed
       

       • Save and wait for DSPO to update
   12. Deploy DSPA
   13. Run Iris Pipeline, Flip Coin pipelines
   14. Make sure the pipeline runs Succeeds
   15. Repeat the above steps but this time check ENABLE_FIPS_IN_CLUSTER checkbox to create a FIPS cluster
2. Comment /integration-tests-ok on this PR to add the verification label
3. This workflow check will automatically pass once the label is added

🔒 Authorization:

Only organization members and owners can use the /integration-tests-ok command.

---

This requirement ensures production stability by verifying integration tests against the latest ODH nightly build.

[nsingla]

/integration-tests-ok

[github-actions]

Test Results

 1 files   1 suites   10m 26s ⏱️
72 tests 33 ✅ 39 💤 0 ❌
81 runs  42 ✅ 39 💤 0 ❌

Results for commit 294a328.

♻️ This comment has been updated with latest results.

[HumairAK]

/integration-tests-ok

[mprahl]

/integration-tests-ok

[nsingla]

/integration-tests-ok

[mprahl]

/integration-tests-ok

[HumairAK]

/integration-tests-ok

[nsingla]

/integration-tests-ok

[dsp-developers]

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-225
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-225
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-225
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-225
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-225
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-225
TESTS: quay.io/opendatahub/ds-pipelines-tests:pr-225