Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Automated cherry pick of #71522: Use Node-Problem-Detector v0.6.0 #71717

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
Merged
merged 1 commit into from
Dec 10, 2018
Merged

Automated cherry pick of #71522: Use Node-Problem-Detector v0.6.0 #71717

merged 1 commit into from
Dec 10, 2018

Conversation

wangzhen127
Copy link
Member

Cherry pick of #71522 on release-1.13.

#71522: Use Node-Problem-Detector v0.6.0

@k8s-ci-robot k8s-ci-robot added do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Dec 4, 2018
@wangzhen127
Copy link
Member Author

/assign @yguo0905
/kind feature
/sig node
/priority important-soon

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. sig/node Categorizes an issue or PR as relevant to SIG Node. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Dec 4, 2018
@wangzhen127
Copy link
Member Author

/assign @Random-Liu
/kind feature

@wangzhen127
Copy link
Member Author

/retest

@yguo0905
Copy link
Contributor

yguo0905 commented Dec 5, 2018

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 5, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wangzhen127, yguo0905

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 Dec 5, 2018
@Random-Liu
Copy link
Member

/lgtm

@wangzhen127
Copy link
Member Author

Patch release managers, PTAL
/assign @tpepper
/assign @aleksandra-malinowska

@aleksandra-malinowska
Copy link
Contributor

Looks good to me. @tpepper I think you mentioned some doubts regarding the release notes - anything that prevents it from merging? If not, let's do it today to get some CI signal over the weekend.

@wangzhen127
Copy link
Member Author

To clarify, the purpose is to make debugging the cluster easier. Node-problem-detector runs on the worker nodes and does not change kubernetes cluster's behavior. What it does is to monitor the node health and report if anything wrong happens.

@aleksandra-malinowska aleksandra-malinowska added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. and removed do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Dec 10, 2018
@k8s-ci-robot k8s-ci-robot merged commit 4fc9908 into kubernetes:release-1.13 Dec 10, 2018
@wangzhen127 wangzhen127 deleted the automated-cherry-pick-of-#71522-upstream-release-1.13 branch December 10, 2018 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mwielgus mwielgus Awaiting requested review from mwielgus

@vishh vishh Awaiting requested review from vishh

Assignees

@tpepper tpepper

@aleksandra-malinowska aleksandra-malinowska

@Random-Liu Random-Liu

@yguo0905 yguo0905

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. 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/feature Categorizes issue or PR as related to a new feature. 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. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/node Categorizes an issue or PR as relevant to SIG Node. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@wangzhen127 @yguo0905 @k8s-ci-robot @Random-Liu @aleksandra-malinowska @tpepper