Epic Goal

Consolidate and deliver all priority post-GA initiatives required to ensure Pruner is stable, performant, scalable, and ready for broader adoption across Konflux, upstream clusters, and customer environments.

Why is this important?

Pruner is a core component responsible for reducing cluster load, preventing etcd bloat, cleaning up stale Tekton resources, and ensuring namespaces remain healthy.
To guarantee long-term reliability and production readiness, key technical debt, performance improvements, and core feature additions must be completed.

Scenarios

This Epic covers improvements in the following areas:

1. Migration to Event-Based Pruner by default
2. Improving pruning performance, scalability, and stability
3. Remediation of stuck resources and finalizers
4. Expanding test coverage (including MicroShift)
5. Increasing upstream contribution and community alignment
6. Installing and evaluating Pruner in Konflux and internal dogfooding clusters
7. Exploring future UX-driven configuration and namespace-level budgeting
8. Documentation, enablement, and operational readiness for Support and SRE teams

Acceptance Criteria (Mandatory)

• CI pipelines run successfully with automated test coverage for all changes
• Release Technical Enablement documentation is prepared and published
• Event-Based Pruner is validated as the future default pruning mechanism
• Performance benchmarks are collected, documented, and validated
• Stuck resource remediation logic is implemented and verified
• MicroShift E2E coverage exists and is integrated into CI
• Upstream contributions for pruner improvements are documented and submitted
• Support & SRE teams receive full operational enablement (Runbooks, Dashboards, Troubleshooting)

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment