Closed wangzhen127 closed 4 months ago
The missing test coverage is for k/k 1.29 and 1.30, which uses NPD v0.8.13
. k/k 1.28 still uses NPD v0.8.9
.
CC @hakman @vteratipally
CC @ndixita
Potential solutions:
Thanks for the suggestions!
I looked into the existing NPD tests and realized that we are using standalone mode already. https://github.com/kubernetes/node-problem-detector/blob/master/test/build.sh#L79C8-L79C41
And we have several test jobs using it, including https://testgrid.k8s.io/sig-node-node-problem-detector#ci-npd-e2e-kubernetes-gce-gci.
So we are good here already.
NPD can be configured to run in either
standalone
ordaemonset
mode. In k/k, the NPDstandalone
mode can be configured and tested by configure.sh#688. However, as part of the kops support, the default mode has been switched fromstandalone
mode todaemonset
mode in PR https://github.com/kubernetes/kubernetes/pull/121007. The PR also bumped NPD version fromv0.8.9
tov0.8.13
.On the other hand, NPD
standalone
mode test has always been relying on tar files ings://kubernetes-release/node-problem-detector/
historically (See configure.sh#L29). And we only have NPD version up tov0.8.10
in the GCS bucket, due to historical release problems. This means we do not even havev0.8.13
tar files in the GCS. Given none of the k/k's release blocking tests fail, we lost the test coverage for standalone mode configuration already.The release problem is being tracked by https://github.com/kubernetes/node-problem-detector/issues/874. We were trying to switch from using
gs://kubernetes-release/
to github's own file hosting (PR https://github.com/kubernetes/kubernetes/pull/123741) and realized the missing test coverage.CC @upodroid @SergeyKanzhelev @Random-Liu @BenTheElder