Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-2228

Implement selection of oauth-proxy image based on cluster version


    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • Logging 5.5.0
    • None
    • Log Storage
    • None
    • Logging (LogExp) - Sprint 217, Logging (LogExp) - Sprint 218, Logging (LogExp) - Sprint 219

      Currently every release of the elasticsearch operator bundles a specific version of oauth-proxy with its releases. During the discussion about a bug it became clear that it might be a good idea to not have a specific version for each release of the operator but instead determine the oauth-proxy version based on the cluster the operator is running in. That way there should be no bugs caused by incompatibility between the oauth-proxy and the oauth-server running in the cluster while also being able to use features of newer versions.

      Acceptance Criteria

      • elasticsearch-operator selects an oauth-proxy image for created deployments (currently only Kibana) based on the cluster version it is running in

      Dev Notes

      • Requires first testing deployment of 5.4 with oauth-proxy:4.8 on OCP 4.8 works OOTB
      • Introduce two env vars: PROXY_IMAGE_4_8, PROXY_IMAGE
      • Read the ClusterVersion resource on startup and decide which env var determines the proxy image:
        • On 4.8: PROXY_IMAGE_4_8
        • On >4.8: PROXY_IMAGE

            sasagarw@redhat.com Sashank Agarwal (Inactive)
            rojacob@redhat.com Robert Jacob
            Giriyamma Karagere Ramaswamy Giriyamma Karagere Ramaswamy (Inactive)
            0 Vote for this issue
            6 Start watching this issue