-
Notifications
You must be signed in to change notification settings - Fork 40.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
remove tpr api access #48353
remove tpr api access #48353
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: deads2k Assign the PR to them by writing Associated issue: 48152 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
LGTM but can we wait until next week to merge it? One of our PMs pointed out to me that the 1.7 announcement will be the first time a lot of people hear about the deprecation. A couple more days without any major concerns being raised should give us more confidence that we won't cause significant pain for users by removing it in 1.8. |
Sure. The bad behavior of TPRs and finalizers is blocking generic GC for discovered resources, but waiting until next week won't make or break it. |
1408db4
to
eeb4e04
Compare
just generated changes in |
lgtm |
Issue has been open over a week. Going ahead with this now. |
Automatic merge from submit-queue (batch tested with PRs 48480, 48353) |
xref #48152
TPR tentacles go pretty deep. This gets us started by removing API access and we'll move down from there.
@kubernetes/sig-api-machinery-misc
@ironcladlou this should free up the GC implementation since TPRs will no longer be present and failing.