Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deprecate crd validation toggle and sync with manifests #1781

Merged
merged 5 commits into from Feb 18, 2022
Merged

Conversation

FxKu
Copy link
Member

@FxKu FxKu commented Feb 15, 2022

Fixes #1497
Fixes #1731
Fixes #1737
Closes #1738

We had some inconsistencies between the CRD manifests and the internal CRD representation that the operator tries to register/update (thanks @bchrobot for the diff list).

This PR deprecates the EnableCRDValidation toggle, since a structural schema is required in v1. This will also fix registering the OperatorConfiguration CRD by the operator.

Last but not least, the PR introduces a new options to configure the categories in which the CRDs are registered - addressing the feature request in #1779. all remains the default. ToDo: Allow configuring categories in helm chart. At the moment, CRDs are not templates.

@FxKu FxKu added this to the 1.8 milestone Feb 15, 2022
@FxKu
Copy link
Member Author

FxKu commented Feb 17, 2022

👍

2 similar comments
@jopadi
Copy link
Member

jopadi commented Feb 18, 2022

👍

@sdudoladov
Copy link
Member

👍

@FxKu FxKu merged commit 3ce0b1e into master Feb 18, 2022
@budimanjojo
Copy link

I think this should be a new release, because I'm still affected by v1.7.1 and it keeps failing to validate some crds.

@lc-guy
Copy link

lc-guy commented Apr 6, 2022

Getting this error as well on latest release, would be nice to get an 1.7.2 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants