Skip to content

Update CSO CSV to use registry.redhat.io pullspecs - #189

Closed
redhat-chai-bot wants to merge 1 commit into
quay:redhat-5.0from
redhat-chai-bot:fix-cso-csv-pullspecs
Closed

redhat-chai-bot wants to merge 1 commit into
quay:redhat-5.0from
redhat-chai-bot:fix-cso-csv-pullspecs

Conversation

@redhat-chai-bot

Copy link
Copy Markdown

The 5.0 CSV uses upstream community pullspecs for the CSO image, while 3.17 and 3.18 use the Red Hat registry pullspecs. This causes olm.allowed_registries_related EC policy violations during the stage release because doozer cannot map the upstream references to the ART-built image.

This PR updates the CSV to use registry.redhat.io/quay/quay-container-security-rhel9-operator for both the containerImage annotation and the deployment container image, matching the pattern used in the 3.17 and 3.18 branches.

Changes

  • containerImage annotation: changed from upstream quay.io/quay/ pullspec to registry.redhat.io/quay/quay-container-security-rhel9-operator
  • Deployment image: changed from upstream quay.io/projectquay/ pullspec to registry.redhat.io/quay/quay-container-security-rhel9-operator

AI-generated. Review for accuracy.

@bcaton85 requested from Slack

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@bcaton85 bcaton85 closed this Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants