In order to the final push to CDN of the tested OVE UI ISO we'll need to create 2 CRs. This must be done each time we want to release, it's not an automatic process by design.

Here is the info from the Konflux bot:
(These steps are performed each time a new version is ready to be shipped to customers.)
1. Manually Create a "Golden" Snapshot After an on-push build pipeline runs successfully and passes QE validation, we must deliberately select that version for release. Creating a manual "golden" Snapshot provides control and traceability over the exact artifact being shipped.
• Action: Create a Snapshot YAML file that points to the exact "vehicle" container image produced by the build-image-index task that has passed QE.
• Source of Truth: Copy the containerImage URL (with the @sha256:... digest) and the source git information from the automatically generated Snapshot that was created and tested.
• Storage: The YAML definition should be stored in the agent-installer-utils repo for peer review and version control.
• Execution: Apply the file directly to the cluster using oc apply -f <snapshot-file.yaml> -n ocp-agent-based-installer-tenant.

2. Manually Create a Release CR to Trigger the Final Release This is the final, manual trigger that initiates the managed release pipeline. This process ensures a human makes the final decision to ship to customers.
• Action: Create a Release CR YAML file.
• Configuration: The Release CR must point to your managed ReleasePlan (from Step 3) and the "golden" Snapshot you created in the previous step.
• Storage: Like the Snapshot, store the YAML definition in agent-installer-utils for review, but do not commit it to konflux-release-data to avoid unintended re-release loops.
• Execution: Apply the Release CR directly to the cluster using oc apply -f <release-file.yaml> -n ocp-agent-based-installer-tenant. Remember that the metadata.name of the Release CR must be unique for every release attempt.