-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
community issues in image-updater pre-v0.16
-
False
-
None
-
False
-
50% To Do, 10% In Progress, 40% Done
-
-
Description of Problem
This epic contains various important issues and PRs in image-updater github community. These issues can be potentially included in the next image-updater release 0.16.0 (starting 2024-10-22).
Additional Info
Problem Reproduction
- <How do we reproduce the problem?>
Reproducibility
- <Always/Intermittent/Only Once>
Prerequisites/Environment
Steps to Reproduce
- ...
Expected Results
Actual Results
- ...
Problem Analysis
- <Completed by engineering team as part of the triage/refinement process>
Root Cause
- <What is the root cause of the problem? Or, why is it not a bug?>
Workaround (If Possible)
- <Are there any workarounds we can provide to the customers?>
Fix Approaches
- <If we decide to fix this bug, how will we do it?>
Acceptance Criteria
- ...
Definition of Done
- Code Complete:
- All code has been written, reviewed, and approved.
- Tested:
- Unit tests have been written and passed.
- Ensure code coverage is not reduced with the changes.
- Integration tests have been automated.
- System tests have been conducted, and all critical bugs have been fixed.
- Tested and merged on OpenShift either upstream or downstream on a local build.
- Documentation:
- User documentation or release notes have been written (if applicable).
- Build:
- Code has been successfully built and integrated into the main repository / project.
- Midstream changes (if applicable) are done, reviewed, approved and merged.
- 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.
- clones
-
GITOPS-5721 Git write back to helm values is incorrect during the first pass and corrupts existing data
- Closed