node-problem-detector
node-problem-detector copied to clipboard
This is a place for various problem detectors running on the Kubernetes nodes.
Hi, I'm using the system-log-monitor to detect the node problem and update the respective NodeCondition, which can match logs in `/dev/kmsg` of specific pattern. I noticed that the NPD updates...
we have observed that when changing our system log monitor configurations to omit a previously watched condition, the condition persists on the node object. I have added a bool flag...
Bumps golang from `d7d795d` to `fa1a01d`. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...
Bumps the actions-all group with 2 updates: [github/codeql-action](https://github.com/github/codeql-action) and [actions/upload-artifact](https://github.com/actions/upload-artifact). Updates `github/codeql-action` from 3.28.11 to 3.28.13 Release notes Sourced from github/codeql-action's releases. v3.28.13 CodeQL Action Changelog See the releases page...
Bumps the k8s group with 2 updates in the / directory: [k8s.io/api](https://github.com/kubernetes/api) and [k8s.io/client-go](https://github.com/kubernetes/client-go). Bumps the k8s group with 2 updates in the /test directory: [k8s.io/apimachinery](https://github.com/kubernetes/apimachinery) and [k8s.io/component-base](https://github.com/kubernetes/component-base). Updates `k8s.io/api`...
The Docker Daemon is no longer supported by Kubernetes. This PR removes corresponding code.
Please update the following library dependencies to latest to resolve the security vulnerabilities. golang.org/x/crypto from v0.25.0 to latest v0.35.0. to resolve https://nvd.nist.gov/vuln/detail/CVE-2025-22869
has anyone thought of adding internal app metrics to show if problem daemons are having any issues? following on from #1003 , i have added a few internal log events...
When using a filelog monitor, the top-level `pluginConfig.message` filter provides a limited stream of log events to be checked against the `rules[].pattern`. I thus expect it to be normal for...