csi-node-driver-registrar is from k8s.gcr.io

[yankay]

According to the docs : https://kubernetes-csi.github.io/docs/node-driver-registrar.html, csi-node-driver-registrar is from k8s.gcr.io. But the is from the https://github.com/hwameistor/helm-charts/blob/main/charts/hwameistor/values.yaml#L1, It's from the Quay.io .

[SSmallMonster]

Hi, @yankay
Thanks for your suggestion.

The registry of the CSI controller images can be modified by specifying the value of the k8simageregistry parameter when deploy with helm.

Why we set qury.io default

qury.io will be faster than k8s.gcr.io in China , but as the default, maybe we should point it to k8s.gcr.io.

The next, we will update the default CSI controller images registry to k8s.gcr.io

[SSmallMonster]

We encountered a problem when modifying the image repository. The CSI node driver register image was migrated from version v2.0.0 to k8s.gcr. io, but the image has not been migrated before(e.x. v1.1.0 we now use), and it still exists in qury.io

If we upgrade the version directly, may face some compatibility problems, and we may need more tests.

[github-actions]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.