resolve osimagestream integration in OKD #5497
Draft
+785
−768
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- What I did
Historically, OKD always tracks the latest version of CentOS Stream, making dual OS stream support unnecessary. Building upon @pablintino's work in #5476, I introduced separate OSImageStream reconciliation behavior for OKD so that it will basically no-op.
- How to verify it
Behavior in OCP should continue to work as it should. Any behaviors around OSImageStreams in OKD should not occur, at least not until we determine what behaviors should occur.
- Description for the changelog
Introduce separate OSImageStream behavior for OKD