Value Statement

Right now, we packaged the oauth-proxy image by ACM and Global hub. but the version is a fixed version. We assume it can support all OCP version with different environment (FIPs or non-FIPs). But it is not true. In ACM 2.11 release, we found that oauth-proxy 4.9 have issue in OCP 4.16 FIPs environment. refer to https://issues.redhat.com/browse/ACM-12455 and https://issues.redhat.com/browse/ACM-12485 We provide a temp solution to bundle oauth-proxy v4.16 for OCP 4.16.

For the longer term, we should fetch the oauth-proxy from OCP environment. It can be guaranteed that the build-in oauth-proxy is working with that OCP version. In this way, we won't meet the compatible issue again.

Definition of Done for Engineering Story Owner (Checklist)

• Get the oauth-proxy from OCP in observability operator
• Test all supported OCP version to ensure it works as design.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.