chore(konflux): add Tekton pipeline definitions for release-v0.17

[jlost]

Summary

Ports .tekton/ pipeline definitions from release-v0.15 to release-v0.17 so Konflux/PaC can trigger image builds on this branch. Without these files, release tags based on release-v0.17 (e.g., odh-v3.4-EA2) do not produce any images.

Changes from release-v0.15 source

• CEL expressions: target_branch == "release-v0.15" -> target_branch == "release-v0.17" (all 8 pull/push files)
• .gitignore: Unchanged (.tekton entry kept; files are force-tracked as on release-v0.15)
• kserve-group-test.yaml: Copied as-is (no branch filter -- triggers on event == "group-test")
• output-image tags: Carried over as-is from release-v0.15 HEAD (:odh-v3.4-EA2)
• Dockerfiles, paths, service accounts, labels: All unchanged

Note: Merging this PR will trigger PaC to build the EA2 images (kserve-controller, kserve-router, kserve-agent, kserve-storage-initializer) tagged :odh-v3.4-EA2 on Quay, since the merge is a push event to release-v0.17 matching the CEL expressions in the .tekton/ files.

After merging, the next step is to re-run the release workflow for kserve with allow_existing_tag: true to bump the Tekton output-image tags to the next release (e.g., odh-v3.4).

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (4)

• main
• master
• incubation
• rhoai

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.

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: db8c32b2-7c04-43d3-9b05-93f51b50e281

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Coding Plan

• Generate coding plan for human review comments

---

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

[vivekk16]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlost, vivekk16

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:

• OWNERS [jlost,vivekk16]

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

[openshift-ci]

@jlost: 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/prow/pr-image-mirror-llmisvc-controller	ff6937b	link	true	/test pr-image-mirror-llmisvc-controller

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.

[spolti]

replaced by #1240

[rhods-ci-bot]

@jlost: The following test has Succeeded:

OCI Artifact Browser URL

View in Artifact Browser

Inspecting Test Artifacts Manually

To inspect your test artifacts manually, follow these steps:

1. Install ORAS (see the ORAS installation guide).
2. Download artifacts with the following commands:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/opendatahub/odh-ci-artifacts:kserve-group-test-dq7s4