-
Notifications
You must be signed in to change notification settings - Fork 96
Bug 1989772: Rebase to k8s 1.22.0-rc.0 #196
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
Conversation
Use the default factory methods to set up metrics for our token authenticator and remote authorizer.
|
@adambkaplan: An error was encountered querying GitHub for users with public email (wewang@redhat.com) for bug 1989772 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
Post "http://ghproxy/graphql": dial tcp 172.30.229.2:80: i/o timeout
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
| RecordRequestTotal: authenticatorfactory.RecordRequestTotal, | ||
| RecordRequestLatency: authenticatorfactory.RecordRequestLatency, |
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.
@p0lyn0mial I believe you added this in kubernetes/kubernetes#99364. Is this the right course of action, or should the metrics be a no-op?
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.
yes if we think the metrics are valuable :)
The delegated AuthN/Z uses the same metrics. Since OCM is not using the generic API library we need to wire them manually.
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.
I'd argue they aren't valuable, going to run with Jawed's current PR implementation.
| RecordRequestTotal: authorizerfactory.RecordRequestTotal, | ||
| RecordRequestLatency: authorizerfactory.RecordRequestLatency, |
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.
@p0lyn0mial likewise this was added in kubernetes/kubernetes#100339 - is this the right course of action? Or should we use a no-op?
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.
same as 85daa33#r695940905
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@adambkaplan: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
/close We don't need the metrics. |
|
@adambkaplan: Closed this PR. DetailsIn 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. |
|
@adambkaplan: This pull request references Bugzilla bug 1989772. The bug has been updated to no longer refer to the pull request using the external bug tracker. DetailsIn 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. |
Rebase ocm to kube 1.22.0 (release candidate)