Objective

Evaluate and implement Final Pipeline as a replacement for nudges in Konflux to reduce noise and resource consumption.

Context

Nudges are currently generating significant noise and resource consumption. Final Pipeline is a Konflux feature that executes at the conclusion of the release workflow, after tenant or managed pipeline completes successfully. This could provide a cleaner, more efficient approach.

Reference

• Final Pipeline Documentation

Scope of Work

1. Research & Feasibility

• Understand current nudge implementation and pain points
• Document resource consumption metrics from nudges
• Evaluate Final Pipeline capabilities vs current nudge behavior
• Key question: Can Final Pipeline work for non-release scenarios (e.g., component bumps triggering operator builds without creating a Release)?

2. Design

• Define migration path from nudges to Final Pipeline
• Identify gaps or scenarios not covered by Final Pipeline
• Document required ReleasePlan configuration changes

3. Implementation

• Configure Final Pipeline in ReleasePlan
• Create/adapt Tekton pipeline for post-release actions
• Test in staging environment

4. Rollout

• Gradual migration from nudges
• Monitor resource consumption improvement
• Document changes for team

Open Questions

• Does Final Pipeline only trigger on Release CRs, or can it work with component bump scenarios that don't create a formal Release?
• What's the current resource consumption baseline from nudges?
• Are there edge cases where nudges are still needed?

Acceptance Criteria

• Feasibility assessment complete (including non-release scenarios)
• Design document approved
• Final Pipeline implemented and tested
• Nudges disabled/removed
• Resource consumption reduced (measurable improvement)
• Team documentation updated