Use JFrog repository with hazelcast.com domain

[jerrinot]

instructions says this helm repo add hazelcast https://hazelcast-charts.s3.amazonaws.com/
we should explore how to have a repository on a nicer and more official-looking URL. something like https://helm.hazelcast.com or https://helm.repository.hazelcast.com.

@alparslanavci is working on Bintray migration so perhaps the new repo could be used for Helm chart hosting too?
Obviosly we would have to deprecate the old repo and make it to send redirects to the new one.

[hasancelik]

If we can provide healthy redirection mech from s3 to JFRog, having a official-looking URL would be good. Otherwise, we need to do so much documentation/README update :)

We moved our chart repo from github to s3 to get metrics about their traffic so @alparslanavci can community metrics tool get some traffic info from JFrog?

[alparslanavci]

JFrog Artifactory has a Helm repository option, but IMO it will be better if we can keep s3 and do a re-direction with something like helm.hazelcast.com. This way, we won't need any changes in metrics collection.

@hasancelik wdyt?

[jerrinot]

will the helm client follow the redirect?

[alparslanavci]

@hasancelik will know it better, but if we migrate to Artifactory, it has already a re-direction at repository.hazelcast.com.

[jerrinot]

Is it a redirection (HTTP 301 or 302) or just a CNAME record in DNS? The former requires a cooperation from clients. The later is transparent (done in DNS resolver)

[alparslanavci]

It is the second (CNAME record in DNS) for repository.hazelcast.com.

[jerrinot]

ok, that should work with all clients. one just have to be carefully with certificates.

[hasancelik]

@alparslanavci I have checked the official doc, adding CNAME record in DNS is enough. As @jerrinot mentioned, old URL will continue to work for helm clients.