Bug 1812489

Summary:	oauth-proxy image cannot be referenced for disconnected installs
Product:	OpenShift Container Platform	Reporter:	Michal Fojtik <mfojtik>
Component:	apiserver-auth	Assignee:	Michal Fojtik <mfojtik>
Status:	CLOSED ERRATA	QA Contact:	scheng
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, bparees, mfojtik, scheng, sttts, xiuwang
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1805250	Environment:
Last Closed:	2020-07-13 17:19:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1805247

Description Michal Fojtik 2020-03-11 12:36:35 UTC

+++ This bug was initially created as a clone of Bug #1805250 +++

+++ This bug was initially created as a clone of Bug #1805247 +++

+++ This bug was initially created as a clone of Bug #1804765 +++

+++ This bug was initially created as a clone of Bug #1804763 +++

Description of problem:

The oauth-proxy image is used by various external products (e.g. OLM operators).  Currently they must reference all their images using SHAs to ensure they can be mirrored for disconnected installs.  However that means they must repackage their operator every time the SHA changes.

It would be better if they can simply reference the current image via an imagestreamtag provided by OCP.

We will introduce a new imagestreamtag that maps to the SHA from the OCP payload for the cluster and OLM components can reference that tag to ensure they are always getting the right image.


Actual results:
There is no oauth-proxy imagestreamtag in the openshift namespace

Expected results:
There will be an oauth-proxy imagestreamtag in the openshift namespace which resolves to the SHA of the oauth-proxy image from the cluster's payload.

Comment 2 Michal Fojtik 2020-03-11 15:23:10 UTC

*** Bug 1804765 has been marked as a duplicate of this bug. ***

Comment 4 errata-xmlrpc 2020-07-13 17:19:39 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409