Areas to cover for Manual testing:

1. Verify the new pruner option that should remove what the old pruner does, verify below events are verify these are removed by new event based pruner
   1. Operator (Batch Process, CronJob based)
   2. Pipelines-as-code (Executes on new pipeline runs)
   3. Results (reconciler based after the deadline expires and log storage is successful, there is a race condition bug )
2. Deploy pruner with Helm charts
3. Make the pipelinerun and taskrun in a stuck state ,and verify the PLR or TR is removed after the provided time elaspsed with new pruner and respective PVCs are removed
4. Validate the configmap with invalid pruner options
5. Verify annotation and label support for namespace-level pruner options
6. Tekton pruner configs should not override values post upgrade
7. Test namespace-level pruner takes priority

E2E Scope:

• Create respective Jira stories to automate the following scenarios:
  • Verify pruner version
  • Happy path with global config for each value and verify PLR and TR are removed and respective PVC
  • Happy path with namespace-level config for each config value
  • Failed and Pending PLR and TR removal
  • Add Pipelineruns with label and annotation, and verify annotation and label support for namespace-level pruner options
  • Validate pruner configuration mismatch post upgrade in Upgrade test

Out of scope for E2E: