This repository was archived by the owner on May 24, 2023. It is now read-only.
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.
Proposed changes
RH certification process doesn't use the newer versions of k8s. This means, CRD
v1
can't be used. The operator-sdk 0.18 introduced this breaking change here operator-framework/operator-sdk#2874 and it generates the CRD withv1
instead ofv1beta1
This makes updating the
operator-sdk
dependency really risky, even if newer versions have more features.. because we can break the certification process, as the new versions have a lot of breaking changes.So for now, we have to go back to an older version unfortunately.
Note: make sure to downgrade your operator-sdk local cli version to 0.17.1 (yes, there's a mismatch in the versions, it has to be 0.17.2 in the dependency and 0.17.1 in the cli tool, this is intentional based on the first comment of https://github.com/operator-framework/operator-sdk/releases/tag/v0.17.1)