bumping helm chart version for mysql changes by @CASL0

README.md

@@ -1,5 +1,5 @@
 # coturn Helm Chart
-<a href="https://github.com/jessebot/coturn-chart/releases"><img src="https://img.shields.io/github/v/release/jessebot/coturn-chart?style=plastic&labelColor=blue&color=green&logo=GitHub&logoColor=white"></a>
+<a href="https://github.com/small-hack/coturn-chart/releases"><img src="https://img.shields.io/github/v/release/small-hack/coturn-chart?style=plastic&labelColor=blue&color=green&logo=GitHub&logoColor=white"></a>
 
 An unofficial [coturn](https://github.com/coturn/coturn) helm chart using the official [coturn docker image](https://hub.docker.com/r/coturn/coturn).
 
@@ -22,7 +22,7 @@ An unofficial [coturn](https://github.com/coturn/coturn) helm chart using the of
 Note that you still need to fill out the [`charts/coturn/values.yaml`](./charts/coturn/values.yaml) (Autogenerated Docs can be found in [`charts/coturn/README.md`](./charts/coturn/README.md)).
 
 ```console
-helm repo add coturn https://jessebot.github.io/coturn-chart/
+helm repo add coturn https://small-hack.github.io/coturn-chart/
 helm install coturn coturn/coturn --values values.yaml
 ```
 

charts/coturn/Chart.yaml

@@ -2,13 +2,13 @@ apiVersion: v2
 name: coturn
 type: application
 description: A Helm chart to deploy coturn
-home: "https://github.com/jessebot/coturn-chart"
-version: 4.3.0
+home: "https://github.com/small-hack/coturn-chart"
+version: 4.4.0
 
 # renovate: image=coturn/coturn
 appVersion: 4.6.2
 sources:
-  - "https://github.com/jessebot/coturn-chart"
+  - "https://github.com/small-hack/coturn-chart"
 
 maintainers:
   - name: "jessebot"

charts/coturn/README.md

@@ -1,10 +1,10 @@
 # coturn
 
-![Version: 4.3.0](https://img.shields.io/badge/Version-4.3.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 4.6.2](https://img.shields.io/badge/AppVersion-4.6.2-informational?style=flat-square)
+![Version: 4.4.0](https://img.shields.io/badge/Version-4.4.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 4.6.2](https://img.shields.io/badge/AppVersion-4.6.2-informational?style=flat-square)
 
 A Helm chart to deploy coturn
 
-**Homepage:** <https://github.com/jessebot/coturn-chart>
+**Homepage:** <https://github.com/small-hack/coturn-chart>
 
 ## Maintainers
 
@@ -14,7 +14,7 @@ A Helm chart to deploy coturn
 
 ## Source Code
 
-* <https://github.com/jessebot/coturn-chart>
+* <https://github.com/small-hack/coturn-chart>
 
 ## Requirements
 
@@ -59,7 +59,7 @@ A Helm chart to deploy coturn
 | image.tag | string | `""` | docker tag for coturn server |
 | labels | object | `{"component":"coturn"}` | Coturn specific labels |
 | mysql.auth.database | string | `"coturn"` | database to create, ignored if existingSecret is passed in |
-| mysql.auth.existingSecret | string | `""` | Use existing secret for password details.  The secret has to contain the keys mysql-root-password, mysql-replication-password and mysql-password |
+| mysql.auth.existingSecret | string | `""` | Use existing secret for password details. The secret has to contain the keys mysql-root-password, mysql-replication-password and mysql-password |
 | mysql.auth.password | string | `""` | password for db, autogenerated if empty & existingSecret empty |
 | mysql.auth.secretKeys.password | string | `"password"` | key in existing Secret to use for coturn user's password |
 | mysql.auth.secretKeys.username | string | `"username"` | key in exsiting Secret to use for the coturn user |
@@ -96,4 +96,4 @@ A Helm chart to deploy coturn
 | service.type | string | `"ClusterIP"` | The type of service to deploy for routing Coturn traffic.   ClusterIP: Recommended for DaemonSet configurations. This will create a              standard Kubernetes service for Coturn within the cluster.              No external networking will be configured as the DaemonSet              will handle binding to each Node's host networking    NodePort:  Recommended for Deployment configurations. This will open              TURN ports on every node and route traffic on these ports to              the Coturn pods. You will need to make sure your cloud              provider supports the cluster config setting,              apiserver.service-node-port-range, as this range must contain              the ports defined above for the service to be created.    LoadBalancer: This was what was originally set for this chart in the                 upstream of this fork, but with no details |
 
 ----------------------------------------------
-Autogenerated from chart metadata using [helm-docs v1.12.0](https://github.com/norwoodj/helm-docs/releases/v1.12.0)
+Autogenerated from chart metadata using [helm-docs v1.13.1](https://github.com/norwoodj/helm-docs/releases/v1.13.1)

charts/coturn/templates/configmap-initdb-scripts.yaml

@@ -1,4 +1,4 @@
----
+{{- if .Values.mysql.enabled }}
 apiVersion: v1
 kind: ConfigMap
 metadata:
@@ -61,3 +61,4 @@ data:
         password varchar(127),
         primary key (name)
     );
+{{- end }}

charts/coturn/values.yaml

@@ -125,7 +125,7 @@ mysql:
     password: ""
     # -- database to create, ignored if existingSecret is passed in
     database: "coturn"
-    # -- Use existing secret for password details. 
+    # -- Use existing secret for password details.
     # The secret has to contain the keys mysql-root-password, mysql-replication-password and mysql-password
     existingSecret: ""
     # Names of the keys in existing secret to use for MySQL credentials