Epic Goal

Use oauth-proxy imagestream within OCP environment instead of bundle a fixed by ACM and Global hub

Why is this important?

We met 2 blockers for oauth-proxy in ACM release 2.5 and 2.11 in the last minutes, because the issue is a compatible issue for new OCP version support.

https://github.com/stolostron/backlog/issues/21176

https://issues.redhat.com/browse/ACM-12455

https://issues.redhat.com/browse/ACM-12485

For the current solution, we assume a fixed version of oauth-proxy can be forward compatible. Sometimes, it is not true. It is better to get the OCP bundled version for us to use.

Scenarios

As a cluster admin,

• I can see the oauth-proxy image matched OCP version is using in the global hub grafana pod.
• I can see the oauth-proxy image matched OCP version is using in the observability grafana pod.

Tasks:

1. Build the logic to get oauth-proxy image from imagestream in global hub operator and observability operator.
2. Remove the oauth-proxy logic from multiclusterhub operator.
3. Remove oauth-proxy image from ACM bundle and Global hub bundle.
4. Remove mirror for ose-oauth-proxy in imagecontentsourcepolicy rhacm-repo

Acceptance Criteria

• Get the oauth-proxy from OCP in global hub operator and observability operator
• Remove the oauth-proxy image references from ACM
• Remove the oauth-proxy images from Global Hub
• Test all supported OCP version to ensure it works as design.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. ...

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.