-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Stop using deprecated functions from k8s.io/apimachinery/pkg/util/wait
#9321
Comments
I'd like to take this on if that's ok? |
Sure! Note that we don't want to this until after the final 1.26 release, which should be in February I believe. Although upstream sometimes gives us bonus releases if there are regressions or vulns. So basically until after a month has gone by with no 1.26 patch. |
That's no problem, I'm just looking for things to get stuck into when I get some free time :) |
Guessing this still can't be completed due to a 1.26 release 2 weeks ago? |
Yeah, we'll have to see if we get a 1.26 release in March. If not, then we can move forward with this. |
The last 1.26 release was 14th March so it’s been over a month now. https://github.com/kubernetes/kubernetes/releases/tag/v1.26.15 |
Yeah, maybe we can do this for June. We are likely not doing anything additional for May due to delays in updating some of our frameworks to 1.30. |
Can i take this? |
Not moving to to-test since this is all tech debt / dropping deprecated internal function calls and there is nothing for QA to validate. |
Closing issue as QA is not needed. |
Upstream kubernetes deprecated several of the
wait.Poll
functions in 1.27.Once 1.26 is end-of-life, we should replace all use of deprecated functions with the suggested 1.27+ replacements, and backport that change to all active branches.
The text was updated successfully, but these errors were encountered: