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

Refactor Pruner code base aligning to the new design

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • Pipelines 1.19.0
    • None
    • Pruner
    • None
    • Pipelines Sprint Pioneers 22, Pipelines Sprint Pioneers 23

      Story (Required)

      Existing Pruner code base https://github.com/openshift-pipelines/tektoncd-pruner has to be updated to incorporate the revised design items (https://docs.google.com/document/d/1FT1kQZFVFmcbhEuMslMdmChBtvF-BB_YMupS-nUmD2Y/edit?tab=t.vddydnsjzth8) 

      Background (Required)

      _In response to the design review feedback for Pruner, the existing approach to drop custom resource in favor of a configmap at namespace level to manage namespace level pruning configurations along with configmap abstraction to accomodate PAC grouping needs, new design has been published with https://issues.redhat.com/browse/SRVKP-6957_ 

      Out of scope

      Code changes to address Watching and handling pruning behavior based on namespace level configmap is out of scope of this story.

      Approach (Required)

      • Introduce a config map processor that loads the revised configmap and updates a local store
      • Controller that watches this confignmap and updates the local stores whenever the configmap is updated
      • PipelineRun Controller that watches and reconciles the pipelineRuns based on the pruning configuration
      • TaskRun Controller that watches and reconciles the pipelineRuns based on the pruning configuration
      •  

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      Are the PipelineRuns and TaskRuns pruned succesfully based on the configmap settings?

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Acceptance criteria are met

              rh-ee-anataraj Anitha Natarajan
              rh-ee-anataraj Anitha Natarajan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 5 minutes
                  5m
                  Remaining:
                  Remaining Estimate - 2 minutes
                  2m
                  Logged:
                  Time Spent - Not Specified Time Not Required
                  Not Specified