Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-5363

consolidate Kiali Quay registry

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Kiali
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      currently we have two registries in Quay

      acceptance criteria: is to find out what are the images used for. Once done, we will create tasks to actually migrate the images and consolidate the registry.

      I think this is mostly due to historic reasons, we should consolidate Kiali builds into one registry. Currently in kiali-qe there are following images:

      • kiali    
        • this repo is used to push images built via jenkins job. It's used for nightly, PR and ad-hoc builds
      • kiali-operator    
        • this repo is used to push images built via jenkins job. It's used for nightly, PR and ad-hoc builds
      • standalone-chrome
        • this is used in selenium testing, its discontinued once we ship OSSM 2.5 (anytime soon)
      • kiali-performance-operator    
        • not needed
      • kiali-olm-cs    
        • not needed
      • integration-tests
        • just a test, not needed
      • mtt  
        • not needed
      • kiali-cypress-tests 
        • just a test, not needed

       


      test images were migrated into core kiali repository 

       

              rhn-support-pmarek Pavel Marek
              rhn-support-pmarek Pavel Marek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: