This commit adds "external" part in redis configuration in helm chart, by this way users can use the existing external Redis rather than using the internal one
1. Fix the pull/push commands showed on UI are incorrect
2. Replace "insecureRegistry" with "externalProtocol"
3. Using the secret rather than pasting text if users want to use the certificate of themselves
4. Refine NOTES.txt
Fixes#5133
Provide more flexibility for ingress controller setting. When the
ingress controller is not exposing 80/443 port, user can set `externalPort` to expose the endpoint of Harbor.
Update the helm chart of Harbor to use 1.5 image. Specifically
`1.5.0-chart-patch` to include the fix to #4496 (for integration reason
this fix will not be merge to release branch).
Verified against kubenetes v1.10.0
Assuming Harbor FQDN is specified as harbor.my.domain by the user,
the Notary server FQDN will be set to notary-harbor.my.domain.
So the user must point both Harbor FQDN and Notary FQDN to the K8s
ingress controller IP in the DNS server.
Fix issue https://github.com/vmware/harbor/issues/4394
* Update Harbor helm chart to deploy Harbor 1.4.0 release
* Change version to 0.1.0 and fix a doc error
* Fix auth_mode default value
* Refine doc and fix a typo
