Ziming

In v0.5.0 there's a known issue that sometimes when deploy harbor, that pod sz-harbor-cluster-harbor-registry-68974d455d-27c5t container `registry` may failed to start, and in log it will report parse /etc/registry/config.yaml failed or...

change dnsNames something like this long, harbor installation will fail `a22bfe0fb89664d67a8dda658ed65028-08c77fe69bd59516.abc.ap-southeast-1.amazonaws1.com`  however if change to a shorter name like `ap-southeast-1.amazonaws1.com`, it will be success. It seems there's some length...