-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Does not compile with apimachinery 1.31 #2927
Comments
@cagataygurturk Was this already changed back in k8s.io/apimachinery? We didn't change anything in controller-runtime and the controller-runtime main branch doesn't have an issue with k8s.io/apimachinery 0.31.0 EDIT: Oh nevermind, We made a change in CR. I wasn't aware (or rather I didn't realize at the time and forgot until now, xref: https://github.com/kubernetes-sigs/controller-runtime/pull/2798/files#diff-3f86588ef108e53ef346d3223ca106ccaa8efe72cb1055489665d7675f3da7b4). What do you mean with "the offending code above got fixed and is waiting to be released"? (do you mean controller-runtime or k8s.io/apimachinery?) Are they going to roll this back in k8s.io/apimachinery 0.31.1? (It's really important because the upcoming CR v0.19 release has to be compatible with 0.31.x) |
/reopen |
@sbueringer: Reopened 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. |
Sounds good. Thx for clarifying! /close |
@sbueringer: 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. |
It seems the changes introduced on https://github.com/kubernetes/kubernetes/pull/121970/files#diff-723a06b5a60646d0e6eeaf63b66f2672b579c72f7008c9ab8529446f20484014R39 broke controller-runtime.
The text was updated successfully, but these errors were encountered: