-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
🐛 Fix Defaulting of the User Agent #2435
Conversation
LGTM. Nit: the |
This broke when we added the HTTP client, because the user-agent gets set by a roundtripper that is constructed within `rest.HTTPClientFor`. As a result, we have to default it before we do that. Currently, it ends up being defaulted to `Go-http-client` which is not very useful.
No real strong opinion either way, but I don't think that version is currently available to us? |
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.
/lgtm
Merging this right now, given that it fixes the underlying bug. @FillZpp let's follow-up on having a more useful user agent with controller-runtime in mind
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, vincepri 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 |
/cherrypick release-0.15 |
@alvaroaleman: #2435 failed to apply on top of branch "release-0.15":
In response to this:
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/test-infra repository. |
The bump is needed to restore fieldmanager value to 'cluster=network-operator' as a fix in this version does it. kubernetes-sigs/controller-runtime#2435 Signed-off-by: Periyasamy Palanisamy <[email protected]>
The bump is needed to restore fieldmanager value to 'cluster-network-operator' as a fix in this version does it. kubernetes-sigs/controller-runtime#2435 Signed-off-by: Periyasamy Palanisamy <[email protected]>
The bump is needed to restore fieldmanager value to 'cluster-network-operator' as a fix in this version does it. kubernetes-sigs/controller-runtime#2435 Signed-off-by: Periyasamy Palanisamy <[email protected]>
The bump is needed to restore fieldmanager value to 'cluster-network-operator' as a fix in this version does it. kubernetes-sigs/controller-runtime#2435 Signed-off-by: Periyasamy Palanisamy <[email protected]>
The bump is needed to restore fieldmanager value to 'cluster-network-operator' as a fix in this version does it. kubernetes-sigs/controller-runtime#2435 Signed-off-by: Periyasamy Palanisamy <[email protected]>
The bump is needed to restore fieldmanager value to 'cluster-network-operator' as a fix in this version does it. kubernetes-sigs/controller-runtime#2435 Signed-off-by: Periyasamy Palanisamy <[email protected]>
This broke when we added the HTTP client, because the user-agent gets set by a roundtripper that is constructed within
rest.HTTPClientFor
. As a result, we have to default it before we do that. Currently, it ends up being defaulted toGo-http-client
which is not very useful.