The following items were mentioned in the ACM 2.14 Retro relating to Konflux improvements (internal to our team): 

1. We are not getting the promised value from konflux yet, we need to evaluate efficiency, communications, security and quality with how we use our new build platform
2. We need to use strategies for dealing with the huge number of konflux chore PRs that land in all of our release branches
3. How can Konflux accelerate our deliveries? Can we automate more things inside it, like BVT tests in IntegrationTestScenarios?
4. Reduce konflux maintenance cost. Currently projects require weekly maintenance to keep konflux builds working. This is very different from before for dev teams.
5. Use the Konflux common pipeline solution to reduce the maintenance cost of Konflux PRs
6. Re enable canary build tests. These were disabled with the konflux migration.  The QE/Jenkins tests are similar but don't run as often and don't have the same visibility.
7. Automate the assisted installer images release as part of the MCE release
8. Find a way to avoid merging new code to branches after code freeze