Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-2020

ClusterTasks should not be "replace"d during upgrades

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • Pipelines 1.6.2
    • None
    • Operator
    • None
    • 1
    • False
    • False
    • Pipelines Sprint 214

      After an upgrade our users might loose existing TaskRuns which use our ClusterTasks (non-versioned) ones.

      Unlike CRDs we do a replace upgrade for ClusterTasks. ie, the non-versioned ones are deleted and recreated during an upgrade. So in that action, all TaskRuns related to those ClusterTasks are going to be garbage collected.

      Need to first verify and then fix, duh!

              piyushgarg001 Piyush Garg
              concaf Shubham Minglani
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: