-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Consolidate and Clean Up Konflux Configuration
-
False
-
-
False
-
To Do
-
SECFLOWOTL-190 - OpenShift GitOps Konflux Enablement
-
60% To Do, 40% In Progress, 0% Done
-
-
Epic Goal
Konflux configuration is currently managed through a large monolithic manifest files in the konflux-release-data gitlab repository. This setup increases complexity and overhead when adding new versions or managing releases.
To streamline configuration management and ensure long-term maintainability, we need to refactor the current setup using Konflux’s recommended practices—particularly the projectstreams feature. Additionally, the release repository should be moved to an appropriate GitHub organization to align with ownership and visibility expectations.
Approach:
- Use projectstreams feature from Konflux to modularize and simplify config setup.
- Move the GitHub repository to a proper organization (maybe redhat-developer).
- Remove obsolete or redundant Konflux configuration files from both GitLab and GitHub repositories to avoid confusion and duplication.
Why is this important?
- ...
Scenarios
- ...
Other Considerations
- <Call out anything explicitly as Out of Scope?>
- <Call out internal and external dependencies?>
- <Are there any known previous works?>
- <Any unanswered questions?>
Definition of Ready
- The epic has been broken down into stories.
- Stories have been scoped.
- The epic has been stack ranked.
Definition of Done
- Code Complete:
- All code has been written, reviewed, and approved.
- Tested:
- Unit tests have been written and passed.
- Integration tests have been completed.
- System tests have been conducted, and all critical bugs have been fixed.
- Tested on OpenShift either upstream or downstream on a local build.
- Documentation:
- User documentation or release notes have been written.
- Build:
- Code has been successfully built and integrated into the main repository / project.
- Review:
- Code has been peer-reviewed and meets coding standards.
- All acceptance criteria defined in the user story have been met.
- Tested by reviewer on OpenShift.
- Deployment:
- The feature has been deployed on OpenShift cluster for testing.
- Acceptance:
- Product Manager or stakeholder has reviewed and accepted the work.