ci: trigger bundle pipeline on daemon/agent image changes

[alebedev87]

The bundle PR pipeline's CEL expression only watched hack/konflux/images/bpfman-operator.txt, so PRs that update the daemon or agent image digest (e.g. Konflux nudge PRs) never triggered a bundle rebuild on the PR itself.

Add hack/konflux/images/bpfman.txt and hack/konflux/images/bpfman-agent.txt to the trigger so all three image digest files cause a bundle pipeline run on pull requests.

🤖 Generated with Claude Code

Summary by CodeRabbit

• CI/CD
  • Pull requests that modify additional Konflux image files can now trigger the appropriate validation pipeline.
  • Updated file-change detection to recognize both bpfman and bpfman-agent image paths.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 2ce6ac4e-e9d7-46ab-94f3-c6d6aa74ef7e

📥 Commits

Reviewing files that changed from the base of the PR and between 398f27d and 8781486.

📒 Files selected for processing (1)

• .tekton/bpfman-operator-bundle-ystream-pull-request.yaml

---

Walkthrough

The Tekton pull request trigger condition now includes two Konflux image paths, allowing changes to those files to satisfy pipeline eligibility.

Changes

Tekton trigger eligibility

Layer / File(s)	Summary
Extend changed-file trigger paths .tekton/bpfman-operator-bundle-ystream-pull-request.yaml	The CEL expression now checks hack/konflux/images/bpfman.txt and hack/konflux/images/bpfman-agent.txt.

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

Possibly related PRs

• openshift/bpfman-operator#2105: Updates the same Tekton trigger condition for the two Konflux image paths.

Suggested labels: approved

🚥 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 matches the change: it updates the bundle pipeline trigger for daemon and agent image changes.
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	Only a Tekton YAML CEL trigger changed; no Ginkgo test files or titles were modified, so no unstable test names were introduced.
Test Structure And Quality	✅ Passed	Only a Tekton YAML trigger changed; no Ginkgo test files or test code were modified, so the check is not applicable.
Microshift Test Compatibility	✅ Passed	Only a Tekton trigger YAML changed; no new or modified Ginkgo e2e tests were added, so MicroShift test compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only a Tekton YAML trigger changed; no Ginkgo tests were added or modified, so SNO test compatibility is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Only a Tekton PipelineRun CEL trigger changed; no deployment, operator, or controller scheduling logic was modified.
Ote Binary Stdout Contract	✅ Passed	PR only edits a Tekton CEL trigger YAML; no process-level Go entrypoints or stdout writes were changed.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only a Tekton YAML trigger changed; no new Ginkgo e2e tests or network/IP logic were added, so the IPv6/disconnected check is not applicable.
No-Weak-Crypto	✅ Passed	Only a Tekton CEL trigger changed; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB or custom crypto/comparison code was added.
Container-Privileges	✅ Passed	Only the Tekton trigger CEL expression changed; no privileged/root/securityContext settings appear in the modified manifest.
No-Sensitive-Data-In-Logs	✅ Passed	Diff only adds two pathChanged entries in a Tekton CEL trigger; no logging code or sensitive-data exposure was introduced.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87

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 [alebedev87]

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