pixiake

/cc @RolandMa1986

/cc @LinuxSuRen @JohnNiang

I think this pull request is more closely linked to https://github.com/kubesphere/kubesphere/pull/3208

`Case1` can use the method that ks-installer to synchronize the images to aliyun repo . https://github.com/kubesphere/ks-installer/blob/28d9ff017d05ffdedabcbe47ec6e68afe9cd2b3e/.github/workflows/sync-release-images.yml#L18 This method uses [`skopeo`](https://github.com/containers/skopeo), which is a very useful images synchronization tool.

/cc @kubesphere/sig-observability

Please try to execute the following command，and check the output. ``` kubectl -n kubesphere-system annotate --overwrite clusterroles system:kubesphere-router-clusterrole meta.helm.sh/release-name=ks-core kubectl -n kubesphere-system annotate --overwrite clusterroles system:kubesphere-router-clusterrole meta.helm.sh/release-namespace=kubesphere-system kubectl -n kubesphere-system...

/cc @RolandMa1986 @pixiake

It seems that the `mutatingwebhookconfigurations` of istio has not been deleted. You can try to remove it and reinstall. ``` kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io istio-sidecar-injector ```

I think the namespace of images should not be changed from `kubespheredev` to `kubesphere`

/hold