-
Notifications
You must be signed in to change notification settings - Fork 40k
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
document /watch prefix deprecation #65147
document /watch prefix deprecation #65147
Conversation
The /proxy prefix paths (deprecated since 1.2) were removed in 1.10 in #59884 I'd like to get deprecation of the /watch prefix paths on the record for 1.11. |
@@ -382,7 +382,7 @@ func (a *APIInstaller) registerResourceHandlers(path string, storage rest.Storag | |||
actions = appendIf(actions, action{"LIST", resourcePath, resourceParams, namer, false}, isLister) | |||
actions = appendIf(actions, action{"POST", resourcePath, resourceParams, namer, false}, isCreater) | |||
actions = appendIf(actions, action{"DELETECOLLECTION", resourcePath, resourceParams, namer, false}, isCollectionDeleter) | |||
// DEPRECATED |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't been deprecated long ago? Can we remove now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it wasn't formally announced, so not yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ic
I was just saying on a api coverage spreadsheet that all these should be just deleted at this point... cc @mbohlool to double check the open api spec |
unfortunately, the endpoints are listed throughout the openapi spec, with no doc-visible deprecation notices. this PR updates it to note the deprecation - https://github.com/kubernetes/kubernetes/pull/65147/files#diff-9ce7ea8441086bf1902b4f936f4601d0 |
@liggitt needs-rebase (also, I'm happy to lgtm after rebase unless you specifically need approval from the aformentioned reviewers) |
0591d57
to
204d70c
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lavalamp, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
204d70c
to
3cf4d77
Compare
New changes are detected. LGTM label has been removed. |
regenerated, retagging |
/retest Review the full test history for this PR. Silence the bot with an |
... sure would have been nice if it said this last time |
/lgtm cancel |
3cf4d77
to
c31faf2
Compare
third time's the charm |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here. |
Why is this deprecated? This is a regression in terms of RBAC |
The top-level path segment access patterns (for proxy and watch) were deprecated in favor of the proxy subresource and the watch query parameter around 1.2
That is incorrect, watch requests are still separately permissioned using the |
No, it is a regression. With the Watch API, you can set watch permissions on a single named resource. With WatchList, you need to give permissions on all resources of a particular type. (Related kubernetes/kubectl#305) |
you can still set watch permissions on a single named item, watched with see #63469 |
closes #65133
these have been marked as deprecated in code for many releases, and all client accesses have switched to using the ?watch=true access method, but documentation was never updated
@kubernetes/sig-api-machinery-api-reviews @kubernetes/api-reviewers