Acceptance Criteria

• Set constant number of replicas for Pipeline and Chains components during testing.
• Run varying concurrency test scenario similar to Testing : Evaluate signing-tr-varying-concurrency scenario with and without chains after fixing Fix stats.sh not considering old deleted PR/TR for calculation
• To answer this question on "Why there is gap between signed/total/finished", plot the following charts or data:
  • PR total - PR Signed = PR Failed

• • TR: We see chains signing failed TR as well since "TR total = TR Signed"
  • Pruner retaining 20 resources for PR, but retaining 200 resources for TR (Maybe because 1 PR has 10 TR)

• Create new test report Varying Concurrency with chains enabled and disabled
• Include following new plots in the report:
  • Plots to answer the Gap qeustion from 2nd point.
  • New Etcd Metric, Controller Count, Workqueue Depth based on https://docs.google.com/document/d/1VjoFPqqdoSB836fqOylA89bC83WO_4nMQFNEeJMewOs/edit?usp=sharing
  • Finished/Deletion durations trend as in https://docs.google.com/document/d/189UlKEtun7mej3G8czybABTR9fKD0yo4zDaqbXsb9Mc/edit?usp=sharing
  • Detailed Stats plot (namespace level + cluster level)