-
Notifications
You must be signed in to change notification settings - Fork 382
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
volumesnapshots CRD has invalid property: anyOf #288
Comments
This is automatically generated by controller-gen. Maybe because it does not know how to interpret
@yuxiangqian should we manually remove a type after it is generated automatically? |
Yeah.. looks like that. we could add |
@xing-yang @yuxiangqian this kubernetes-sigs/controller-tools#328 has some details on what we are facing. for now, adjusting the CRD looks to be the way. I can send a PR for the same if we are in agreement. |
c3beea5#diff-f816aba0495ad43b0e3b8b097e94a8d2 |
The existing code was generated automatically by controller-gen. @yuxiangqian did you have to manually set this to "type: string" in 2.0? Otherwise, this is a change in behavior in controller-gen. This is what we have in release-2.0: Should we just manually modify this and set to "type: string" instead? |
/assign humblec |
@yuxiangqian Yes, I did and once I have a commit to update the controller gen to v0.3.0, if I run update-crd.sh, below is the only change:
The document says about, removing the newly added |
Ping, is there any update? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Hi @xing-yang , can you tell how did you fix it? I just wanted to understand how |
We made a manual change to remove "integer" and keep "string". It is documented in the README: |
Thank you @xing-yang |
What happened:
volumesnapshots CRD has invalid property: anyOf
How to reproduce it (as minimally and precisely as possible):
volumesnapshots.snapshot.storage.k8s.io
CRD.Environment:
kubectl version
): v1.16.8The text was updated successfully, but these errors were encountered: