-
Notifications
You must be signed in to change notification settings - Fork 53
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
operator-courier is not able to validate spec.versions, looks only for deprecated spec.version #163
Comments
This issue prevents operator-courier from validating CRDs generated using operator-sdk v0.17.0 when the |
The issue is also found when validating our new placmentrule CRDs generated by operator-sdk v 0.18.0 operator-courier is still looking for the deprecated spec.version instread of spec.versions. Hope the issue will be fixed in operator-courier ASAP. Or all the new CRDs generated by latest operator-sdk will not pass the operator-courier validation and will not be abled to be uploaded to operator community.
and Here is the CRD for the ref
|
Running operator-courier verify fails to validate crd with spec.versions and looks only for deprecated spec.version
ERROR: crd spec.version not defined.
Expected:
operator courier should be able to validate both spec.versions and deprecated spec.version with a warning message.
link to show deprecated version and new versions
https://github.com/kubernetes/apiextensions-apiserver/blob/9f17d72d862ef8e7e718fb15395f34e9512e2842/pkg/apis/apiextensions/types.go#L40
The text was updated successfully, but these errors were encountered: