[IKRedHat]

Summary

Adds RELATED_IMAGE_RHAII_VLLM_CPU_PZ_* entries to the ClusterServiceVersion manifest to resolve ImagePullBackOff blocker (RHOAIENG-88193) and enable proper digest injection by OLM for the vLLM CPU Power/Z runtime template.

Context

This PR is part of the vLLM CPU Power/Z AIPCC migration (RHAI-121 Epic, RHAISTRAT-2304 parent). Related PRs have already merged:

• opendatahub-operator chore(deps): update odh-operator-v2-16 to c25703d #3996 (RHAI-455) — Added RELATED_IMAGE_RHAII_VLLM_CPU_PZ_* environment variable declarations to handler.go
• odh-model-controller chore(deps): update odh-operator-v2-17 to f2524cd #925 (RHAI-455) — Switched vllm-cpu-runtime-template from $(vllm-cpu-image) to $(vllm-cpu-pz-image)

However, the CSV is currently missing these entries, causing the template parameter to resolve to a placeholder digest instead of the actual multi-arch image. This blocks P/Z deployment with ImagePullBackOff errors.

Changes

Adds three new entries to bundle/additional-images-patch.yaml:

• RELATED_IMAGE_RHAII_VLLM_CPU_PZ_IMAGE
• RELATED_IMAGE_RHAII_VLLM_CPU_PZ_FAST_1_IMAGE
• RELATED_IMAGE_RHAII_VLLM_CPU_PZ_FAST_2_IMAGE

All entries use the x86 CPU image digest as a placeholder, following the atomic swap pattern established during vLLM Gaudi AIPCC migration (RHAI-120, PR #18857).

Test Plan

• Verify CSV generation includes the new RELATED_IMAGE entries
• Confirm vllm-cpu-runtime-template resolves to actual digest (not placeholder)
• Deploy on P/Z hardware once image is available (RHAI-457)

Resolves: RHAI-456
Parent Epic: RHAI-121
Blocker: RHOAIENG-88193

[github-actions]

Post-Codefreeze Gatekeeper — FAILED (evaluation)

Advisory only — this check does not block merging. Please review the results before merging.

Target branch: rhoai-3.6-ea.2
Required Jira version: 3.6 EA2 RHOAI RELEASE

❌ The following issues were found:

• RHOAIENG-88193:
  • fixVersion does not include 3.6 EA2 RHOAI RELEASE (found: 3.6 EA1 RHOAI RELEASE)
  • Release Blocker is not set, expected Approved

---

_{After resolving issues, push a commit, re-edit the PR description, or add the run-gatekeeper label to re-trigger this check.}