Uploaded image for project: 'OpenShift Image Registry'
  1. OpenShift Image Registry
  2. IR-228

Spread registry across multiple zones


    • Spread registry across multiple zones
    • False
    • False
    • Green
    • Done
    • Impediment
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      Just need to close docs tracker

      Just need to close docs tracker

      Epic Goal

      • Make the image registry distributed across availability zones.

      Why is this important?

      • The registry should be highly available and zone failsafe.


      1. As an administrator I want to rely on a default configuration that spreads image registry pods across topology zones so that I don't suffer from a long recovery time (>6 mins) in case of a complete zone failure if all pods are impacted.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.

      Dependencies (internal and external)

      1. Pod's topologySpreadConstraints

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: https://github.com/openshift/cluster-image-registry-operator/pull/730
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

            fmissi Flavian Missi
            obulatov@redhat.com Oleg Bulatov
            Keenon Lee Keenon Lee
            0 Vote for this issue
            4 Start watching this issue