Uploaded image for project: 'Cloud Infrastructure Security & Compliance'
  1. Cloud Infrastructure Security & Compliance
  2. CMP-3454

Create disconnected jobs for File Integrity Operator

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • Quality / Stability / Reliability
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • CMP Sprint 101, CMP Sprint 102, CMP Sprint 103, CMP Sprint 105, CMP Sprint 106

      For disconnected testing, operator teams heavily rely on CI workflows

      The QE CI env (cucushift Prow CI workflows, and flexy-install Jenkins jobs) has following known gaps when it comes to installing operators that have onboarded to Konflux.

      • Operators are no longer shipped into the brew registry (brew.registry.redhat.io), while brew is the source of the qe-app-registry catalog source.
      • For QE CI disconnected clusters, there are only pre-defined `6002/6001/5000` ports opened for mirror registry. Script in Prow - ignition/bastionhost/ignition-bastionhost
        • 5000 is for the actual mirror registry that hosted along with cluster provision
        • 6001 is for `quay.io`
        • 6002 is for `brew.registry.redhat.io`
        • The latter two serve as a bastion proxy registry. (Images are not actually mirrored to that registry, instead they are pulled through the proxy from the brew.)

      As we have onboarded to Konflux, the above process doesn't work any more. Need to create our own steps for disconnected testing.

              xiyuan@redhat.com Xiaojie Yuan
              xiyuan@redhat.com Xiaojie Yuan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: