node-problem-detector pods stuck in pending state about kubernetes HOT 2 CLOSED

Thanks for the reporting this issue. Exactly, it is related to a missing "node-problem-detector" tag on GCR.
We are not going to rollback the chart installation to the latest working tag now, since it doesn't affect cluster core functionality.
But if it blocks something, you can edit the appropriate DaemonSet manually, setting "node-problem-detector:v0.8.10" tag there.

$ kubectl get ds node-problem-detector -o yaml
...
        image: k8s.gcr.io/node-problem-detector/node-problem-detector:v0.8.11
        imagePullPolicy: IfNotPresent
        name: node-problem-detector
...

Good chances that it will be fixed in the upstream soon.

from kubernetes.

This issue was fixed in upstream, and a prevention for such issue was pushed to 1.22.12, 1.23.10, 1.24.4 builds — current stable versions, published in September

from kubernetes.