Alex Zheng

A `--global.registryCredential` is also needed for security.

I guess 99% of user would stick to the existing name convention. Of course, we can always use `sed` to change all the registries. But `registry, pullpolicy and, regcred` are...

Another thing is that, in our platform, we generate web GUI forms for each value.yaml. That's why we would like a single GUI entry for users to change `registry, pullpolicy...

Recommend using the same example cluster as in `quick_start`.

If the problem cannot be avoided, please consider changing `storageNodes` to `initialStorageNodes`, and find a way to prevent it from being changed after first helm install. ``` # initialStorageNodes means...

Suggest improving LDC to allow multiple node name in a single yam: ``` apiVersion: hwameistor.io/v1alpha1 kind: LocalDiskClaimBatch metadata: name: mybatch nodeNames: - k8s-worker-1 - k8s-worker-2 description: diskType: HDD ```

Per https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#some-caveats-and-explanations > There is no support at this time for upgrading or deleting CRDs using Helm. This was an explicit decision after much community discussion due to the danger...

Found a workaround ``` $ helm template helm/hwameistor \ -s templates/post-install-claim-disks.yaml \ --set storageNodes='{k8s-worker-3,k8s-worker-4,k8s-worker-5}' \ | kubectl apply -f - ```

It is currently so for the purpose of clarification. There should eventually be a script for safe uninstallation.

hi, @yasker I've submitted [](https://github.com/cncf/tag-storage/pull/76) which includes updating Longhorn as an incubating project. Regards