Goal: OpenShift administrators will be able to install Jeager using the operator in a OpenShift cluster disconnected from the internet.

Problem: Customers with stringent security standards often do not allow access to the internet from production system environments. As currently implemented, the Jaeger operator will not allow an administrator to install or update Jaeger without access to the internet.

Why is this important: Many OpenShift customers have need clusters in secure environments, and all Red Hat operators are working to support the use case.

Dependencies (internal and external):

Prioritized epics + deliverables (in scope / not in scope):

Estimate (XS, S, M, L, XL, XXL):

Previous Work:
Developers can work with Operator catalogs hosted on a container registry

Customers:

Open questions:
1) The OpenShift services team is pushing an April deadline for this work. Is that timeline realistic?
2) Current blocker (for Service Mesh and Jaeger) is use of OAuth Proxy image - if we hardcode a SHA for this image in the Jaeger operator, as we don't manage/release this image, currently there is no process for being informed when a new Jaeger release would be required due to OAuth Proxy CVE. kconner@redhat.com has raised this issue with OLM team to try to get a solution, but no progress as far as I am aware.
3) Just from 1.16 onwards, or backport for 1.13.1 version used in Service Mesh 1.0?