Closed elchenberg closed 3 months ago
Is it safe to use anyway?
Yes. 😄
And actually fixes an arm support problem which previous tag has.
And actually fixes an arm support problem which previous tag has.
And many security related issues.
Security issues such as......?
Newer base image, newer dependencies, newer Go. You can try running a container image scanner on .13, .14 and .15.
You can try running a container image scanner on .13, .14 and .15.
Are you suggesting that users need to reverse-engineer your release notes?
It's missing the log-counter
binary https://github.com/kubernetes/node-problem-detector/issues/854
when enable network-problem-monitor.json
i see error:
Failed to unmarshal configuration file "/config/network-problem-monitor.json": json: cannot unmarshal number into Go struct field MonitorConfig.pluginConfig of type string
when enable /config/system-stats-monitor.json
i see error:
No create function found for plugin ""
only /config/kernel-monitor.json
, /config/docker-monitor.json
and /config/systemd-monitor.json
works for me
k8s version: 1.21
image: registry.k8s.io/node-problem-detector/node-problem-detector:v0.8.15
Please check monitors:
/close
k/k is using NPD v0.8.16 already and there is a plan to bump to v0.8.18 after code freeze. You can try the new versions. Feel free to file new issues if the new version does not work.
@wangzhen127: Closing this issue.
There is a two weeks old v0.8.15 tag. In contrast to all the other (recent) tags it is not a verified commit and it is not a release. Is it safe to use anyway?