-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Subresource for metadata #54269
Comments
cc @kubernetes/sig-api-machinery-feature-requests |
@smarterclayton already has a "alternative object representation" proposal which covers metadata, I think? But maybe it is not separately permissioned. |
Unfortunately both list and watch can't use subresources, so we'd still
need another mechanism.
On Oct 23, 2017, at 3:47 PM, Daniel Smith <notifications@github.com> wrote:
@smarterclayton <https://github.com/smarterclayton> already has a
"alternative object representation" proposal which covers metadata, I
think? But maybe it is not separately permissioned.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#54269 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p5p9RJNAEy1TXbLVcF8Z6pi7bCbVks5svO1agaJpZM4QADcH>
.
|
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
/remove-lifecycle stale |
This is a tracker to consider the idea of a subresource for object metadata. In particular, for Secrets, you may want to grant a controller permission to read/edit metadata without granting access to the data.
Forked from https://github.com/kubernetes/community/pull/1163/files#r143342579:
@smarterclayton wrote:
@bgrant0607 wrote:
The text was updated successfully, but these errors were encountered: