🐛 CRD upgrade safety ratcheting #2123
Draft
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.
Description
This fixes a bug in the CRD upgrade preflight safety check that causes errors to be reported even when schemas of a CRD have not changed between bundle versions.
The current logic of the CRD checker always reports all issues found in the rountrippability between versions in the new CRD. However if those exact same problems exist in the existing CRD, then the upgrade is not making the situation any worse, so the check should not fail.
NOTE: I have this setup as a WIP because I don't want to use my fork's implementation. We should wait until kubernetes-sigs/crdify#32 merges, and then bump our crdify dependency to pull the fix in.
Reviewer Checklist