Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-205

Remove and deprecate registry deployment dependency for backup of internal images

    XMLWordPrintable

Details

    • Epic
    • Resolution: Done
    • Minor
    • OADP 1.1.0
    • None
    • None
    • Remove registry as dependency of OADP
    • False
    • False
    • To Do
    • ToDo
    • 100
    • 100% 100%
    • 0
    • 0
    • 0
    • Untriaged

    Description

      QE verification: Run regression test that backup/restore of applications that leverage internal images (imagestreams) and confirm that the images are populated into backup storage.

      Upgrade from 1.0.x to 1.1.0 should verify that the registry deployments are deleted for each BSL.

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MIG-1202 Upgrade legacy operator Velero openshift plugin to deprecate registry pod usage

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • New

          Bug - A problem that impairs or prevents the functions of the product. OADP-586 registry deployment still exists on 1.1 build, and the registry pod gets recreated endlessly

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OADP-532 Different registry maybe used to backup images than intended.

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OADP-553 registry incompatible with eu-north-1 s3 region

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. OADP-602 Support GCP for openshift-velero-plugin registry

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OADP-194 Remove the registry dependency from OADP

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OADP-195 OADP registry dependency is insecure

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OADP-363 Design plugin registry alternative to registry deployment for image backup workflow

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OADP-183 Registry pod crashes with CrashLoopBackOff for some invalid/unavailable parameters

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          links to

          GitHub openshift/oadp-operator#743: OADP-205: Remove registry deployment in favor of plugin enhancement

          GitHub openshift/openshift-velero-plugin#145: OADP-205: Implement registry inside openshift-velero-plugin

          GitHub openshift/openshift-velero-plugin#154: OADP-205 Fetch and decode secret for registry plugin environment

          GitHub openshift/openshift-velero-plugin#155: OADP-205 Do not skip restore of imagestream when not using plugin registry

          GitHub openshift/openshift-velero-plugin#190: oadp-1.0: OADP-1650 Add annotation to exclude build pod volumes during backup (#189)

          Activity

            People

              tkaovila@redhat.com Tiger Kaovilai
              rhn-engineering-dymurray Dylan Murray
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: