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

Reconciler and Controller based pruner for better performance

XMLWordPrintable

    • Reconciler and Controller based pruner for better performance
    • 21
    • False
    • None
    • False
    • To Do
    • SECFLOWOTL-126 - Ship Reconciler and Controller based consistent pruner for all
    • 60% To Do, 0% In Progress, 40% Done
    • 21

      Epic Goal

      • R&D on pruner based on its own reconciler to have better overall performance.
      • We can also try if we can remove cronjob and perform pruning from reconciler itself (if we are not over killing operator)

      Why is this important?

      • With initial implementation there were n number of containers created for n namespaces, which was resource heavy and made the overall cluster slow.
      • This got better with fix  (https://github.com/tektoncd/operator/pull/805) where we spawn one container to run all the pruning commands.
      • We need to figure out if there are other way to make it better.

      Acceptance Criteria (Mandatory)

      • Pruning based on reconciler if its faster and handle complex configurations.

       

      Previous Story : https://issues.redhat.com/browse/SRVKP-2159

              jkandasa-rh Jeeva Kandasamy
              pradkuma PRADEEP KUMAR (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: