mariadb chart naming convention

[nomisbeme]

$ helm install mariadb-cluster/
kindly-bobcat

$ kubectl get svc
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
gangly-gorilla-wildfly 10.227.243.59 146.148.61.7 80/TCP,9990/TCP 6m
hazy-anaconda-apache 10.227.244.60 104.197.103.69 80/TCP,443/TCP 16m
kindly-bobcat-master 10.227.247.187 3306/TCP 20s
kindly-bobcat-slave 10.227.255.50 3306/TCP 20s
kubernetes 10.227.240.1 443/TCP 1h

Names should reflect the application launched:
e.g. kindly-bobcat-mariadb-master, kindly-bobcat-mariadb-slave

[sameersbn]

In kubernetes/helm each deployment is assigned a release name which can be specified using the --name arg to helm install. When not specified a random name is generated, kindly-bobcat in this case.

[prydonius]

@sameersbn indeed, but we may still want to add mariadb in the name for ease of identification. The only issue is if the helm generated name is too long and master/slave get's cut off, then we will have a duplicate name issue.

[sameersbn]

The only issue is if the helm generated name is too long and master/slave get's cut off, then we will have a duplicate name issue.

@prydonius That was the primary reason to drop mariadb from the names in the mariadb-cluster chart. I'll revisit the chart to see how the naming can be improved.