[stable/node-problem-detector] Use registry.k8s.io (deliveryhero#457)

stable/node-problem-detector/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v1
 name: node-problem-detector
-version: "2.3.3"
+version: "2.3.4"
 appVersion: v0.8.12
 home: https://github.com/kubernetes/node-problem-detector
 description: |

stable/node-problem-detector/README.md

@@ -1,6 +1,6 @@
 # node-problem-detector
 
-![Version: 2.3.3](https://img.shields.io/badge/Version-2.3.3-informational?style=flat-square) ![AppVersion: v0.8.12](https://img.shields.io/badge/AppVersion-v0.8.12-informational?style=flat-square)
+![Version: 2.3.4](https://img.shields.io/badge/Version-2.3.4-informational?style=flat-square) ![AppVersion: v0.8.12](https://img.shields.io/badge/AppVersion-v0.8.12-informational?style=flat-square)
 
 This chart installs a [node-problem-detector](https://github.com/kubernetes/node-problem-detector) daemonset. This tool aims to make various node problems visible to the upstream layers in cluster management stack. It is a daemon which runs on each node, detects node problems and reports them to apiserver.
 
@@ -58,7 +58,7 @@ helm install my-release deliveryhero/node-problem-detector -f values.yaml
 | hostPID | bool | `false` |  |
 | image.digest | string | `""` | the image digest. If given it takes precedence over a given tag. |
 | image.pullPolicy | string | `"IfNotPresent"` |  |
-| image.repository | string | `"k8s.gcr.io/node-problem-detector/node-problem-detector"` |  |
+| image.repository | string | `"registry.k8s.io/node-problem-detector/node-problem-detector"` |  |
 | image.tag | string | `"v0.8.12"` |  |
 | imagePullSecrets | list | `[]` |  |
 | labels | object | `{}` |  |

stable/node-problem-detector/values.yaml

@@ -55,7 +55,7 @@ logDir:
   pod: ""
 
 image:
-  repository: k8s.gcr.io/node-problem-detector/node-problem-detector
+  repository: registry.k8s.io/node-problem-detector/node-problem-detector
   tag: v0.8.12
   # image.digest -- the image digest. If given it takes precedence over a given tag.
   digest: ""