-
Notifications
You must be signed in to change notification settings - Fork 64
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
Use kube-codegen.sh
instead of generate-groups.sh
when moving to k8s.io api 0.28+
#336
Comments
Related: #335 |
The Kube v0.30 removed the Knative already rolled to Kube v0.30, for example: knative/serving#15462, knative/eventing#8126, so this essentailly prevents changes to any Knative CRDs. As discussed in the Productivity WG, I will create a generate-groups like tool in Knative ASAP, and notify Knative working groups on migration steps in all the Knative projects, that use code-gen. /assign |
Thanks a lot, @cardil |
Some maintainers already started doing the migration to kube_codegen.sh script:
And because it looks like it shouldn't be super hard, we decided it makes sense to just go with it, so the interim generate-groups.sh shim (that I proposed on Productivity WG) wouldn't be required. We created the doc to track the migration effort: https://docs.google.com/spreadsheets/d/12OG7kLYlJIz-vOKihdtG1Vtrg0OsD8vF_umJLFK0_kQ /close |
@cardil: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
As of
k8s.io/[email protected]
, the scriptgenerate-groups.sh
is deprecated and we should move to usingkube-codegen.sh
The text was updated successfully, but these errors were encountered: