Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Manually cherry pick of #83427: Fix double counting issue for request metrics on timeout #84777

Merged
merged 1 commit into from
Nov 7, 2019
Merged

Manually cherry pick of #83427: Fix double counting issue for request metrics on timeout #84777

merged 1 commit into from
Nov 7, 2019

Conversation

RainbowMango
Copy link
Member

@RainbowMango RainbowMango commented Nov 5, 2019 •
edited
Loading

What type of PR is this?
/kind bug
/priority important-soon

What this PR does / why we need it:
Cherry pick #83427

Which issue(s) this PR fixes:

Special notes for your reviewer:
Please ignore my wrong branch name, it should be against release-1.15.

Does this PR introduce a user-facing change?:

Adds a metric apiserver_request_error_total to kube-apiserver. This metric tallies the number of request_errors encountered by verb, group, version, resource, subresource, scope, component, and code.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/cc @logicalhan @lavalamp @tpepper

@RainbowMango
Cherry-pick kubernetes#83427
412cbe0 
Fix double counting issue for request metrics on timeout.
@k8s-ci-robot k8s-ci-robot added this to the v1.15 milestone Nov 5, 2019
@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. labels Nov 5, 2019
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. area/apiserver sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Nov 5, 2019
@RainbowMango
Copy link
Member Author

/test pull-kubernetes-kubemark-e2e-gce-big

logicalhan
logicalhan approved these changes Nov 5, 2019
View reviewed changes
Copy link
Member

@logicalhan logicalhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 5, 2019
@lavalamp
Copy link
Member

lavalamp commented Nov 5, 2019

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lavalamp, RainbowMango

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 5, 2019
@tpepper tpepper added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 7, 2019
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. label Nov 7, 2019
@k8s-ci-robot k8s-ci-robot merged commit 0869af6 into kubernetes:release-1.15 Nov 7, 2019
@RainbowMango RainbowMango deleted the manually-cherry-pick-of-#83427-upstream-release-1.16 branch December 10, 2019 01:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@logicalhan logicalhan logicalhan approved these changes

@lavalamp lavalamp Awaiting requested review from lavalamp

@tpepper tpepper Awaiting requested review from tpepper

Assignees

@logicalhan logicalhan

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/apiserver cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
v1.15
Development

Successfully merging this pull request may close these issues.
5 participants
@RainbowMango @lavalamp @k8s-ci-robot @logicalhan @tpepper