Uploaded image for project: 'Migration Toolkit for Red Hat Openshift Project Lead'
  1. Migration Toolkit for Red Hat Openshift Project Lead
  2. MTRHO-117

Figure out how we want to specify images for upstream/vs. downstream

    XMLWordPrintable

Details

    • False
    • Hide

      None

      Show
      None
    • False
    • No

    Description

      We are likely going to need to replace upstream images with downstream images, so we'll need to decide how we want to do so and implement it. For the most part this can be as simple as specifying them using env vars on the operator deployment. These can then be updated in an automated fashion during the downstream buils.

      See for instance on mig-operator:
      https://github.com/konveyor/mig-operator/blob/master/deploy/olm-catalog/bundle/manifests/crane-operator.v99.0.0.clusterserviceversion.yaml#L681-L732

      In some cases the deployments using the containers aren't directly launched by the operator (rsync-transfer as a for instance). In these cases we have to think about how we want to pass these in.

      I believe crane-runner is also hard coded in a bunch of cluster tasks so we'll have to fix that as well.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              migeng.robot MigEng Robot
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: