-
Notifications
You must be signed in to change notification settings - Fork 1.2k
✨ Add FieldOwner field to client.Options #3389
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
✨ Add FieldOwner field to client.Options #3389
Conversation
|
Hi @aerfio. Thanks for your PR. I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
/ok-to-test |
alvaroaleman
left a comment
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.
seems okay to me. @sbueringer WDYT? Odds are we will end up adding most/all of the wrappers in here.
/hold
|
LGTM label has been added. Git tree hash: 439b4f17408bf1e5554a84542279b4d791b14840
|
|
@alvaroaleman My plan is to actually create the same PR but for the |
All good from my side, just a minor point on the godoc: #3389 (comment) |
|
Thank you very much! /lgtm |
|
LGTM label has been added. Git tree hash: 2007aae2b26d584377139437f6e8769c40a0a2f2
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aerfio, alvaroaleman, sbueringer 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 |
Introduce FieldOwner field to client.Options, to allow users to set it once, without doing it like that:
The main reason however is the ability to set it in manager creation, so that the client we get from it using
mgr.GetClient()is already correctly configured. Otherwise I have to plumb the client manually or use following code:But the documentation of
NewClientstates that it's a low level primitive and should not be used unless you know what you're doing, so I'd rather not overwrite default client creation fn