-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[addons] Introduce NodeProblemDetector #11381
Conversation
Hi @dntosas. Thanks for your PR. I'm waiting for a kubernetes 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/test-infra repository. |
2ec87e3
to
0a8268c
Compare
92ec890
to
73899ee
Compare
/ok-to-test |
/assign @mikesplain |
/assign @olemarkus |
upup/pkg/fi/cloudup/bootstrapchannelbuilder/bootstrapchannelbuilder.go
Outdated
Show resolved
Hide resolved
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.
A few more questions if you don't mind:
- Why not also add the limits together with the requests?
- Why not use the tolerations from the original manifest:
- effect: NoSchedule
operator: Exists
- effect: NoExecute
operator: Exists
upup/models/cloudup/resources/addons/node-problem-detector.addons.k8s.io/k8s-1.17.yaml.template
Outdated
Show resolved
Hide resolved
|
We a) avoid setting any default limits. b) don't add options for setting limits where limits can cause harm. Such as CNIs OOMing over a bad limit. For addons such as this, I think exposing limits is fine. |
pkg/apis/kops/componentconfig.go
Outdated
// Default: false | ||
Enabled *bool `json:"enabled,omitempty"` | ||
// Image is the NodeProblemDetector docker container used | ||
// Default: k8s.gcr.io/node-problem-detector/node-problem-detector:v0.8.8 |
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 think we can remove this line. Seems too much effort to maintain it.
// Default: k8s.gcr.io/node-problem-detector/node-problem-detector:v0.8.8 |
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 still see the line here and in a few other places.
upup/pkg/fi/cloudup/bootstrapchannelbuilder/bootstrapchannelbuilder.go
Outdated
Show resolved
Hide resolved
@dntosas Any chance you have time to address the remaining nits? |
y sure, pushed ^^ adding the limits also |
aec26c6
to
340a5eb
Compare
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.
Let's keep the limits same as in the source template, unless there is a reason for them to differ.
} | ||
|
||
if npd.MemoryRequest == nil { | ||
defaultMemoryRequest := resource.MustParse("32Mi") |
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.
defaultMemoryRequest := resource.MustParse("32Mi") | |
defaultMemoryRequest := resource.MustParse("80Mi") |
} | ||
|
||
if npd.CPULimit == nil { | ||
defaultCPULimit := resource.MustParse("100m") |
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.
defaultCPULimit := resource.MustParse("100m") | |
defaultCPULimit := resource.MustParse("10m") |
} | ||
|
||
if npd.MemoryLimit == nil { | ||
defaultMemoryLimit := resource.MustParse("128Mi") |
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.
defaultMemoryLimit := resource.MustParse("128Mi") | |
defaultMemoryLimit := resource.MustParse("80Mi") |
pkg/apis/kops/componentconfig.go
Outdated
// Default: false | ||
Enabled *bool `json:"enabled,omitempty"` | ||
// Image is the NodeProblemDetector docker container used | ||
// Default: k8s.gcr.io/node-problem-detector/node-problem-detector:v0.8.8 |
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 still see the line here and in a few other places.
Node Problem Detector aims to make various node problems visible to the upstream layers in the cluster management stack. It is a daemon that runs on each node, detects node problems and reports them to apiserver so to avoid scheduling new pods on bad nodes and also easily identify which are the problems on underlying nodes. Project Home: https://github.com/kubernetes/node-problem-detector Signed-off-by: dntosas <ntosas@gmail.com>
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.
Thanks @dntosas!
👍
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
/retest Review the full test history for this PR. Silence the bot with an |
2 similar comments
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
1 similar comment
/retest |
Node Problem Detector aims to make various node problems visible to
the upstream layers in the cluster management stack. It is a daemon
that runs on each node, detects node problems and reports them to apiserver
so to avoid scheduling new pods on bad nodes and also easily identify
which are the problems on underlying nodes.
Project Home: https://github.com/kubernetes/node-problem-detector
Signed-off-by: dntosas ntosas@gmail.com