Merge pull request #59 from averbis/56-parametrize-registry-url

56 parametrize registry url

charts/health-discovery/Chart.yaml

@@ -1,6 +1,6 @@
 name: health-discovery
 description: Health Discovery is the healthcare text mining and machine learning platform for analyzing large amounts of patient data
-version: 7.1.1
+version: 7.1.2
 apiVersion: v1
 keywords:
   - health-discovery

charts/health-discovery/README.md

@@ -55,16 +55,23 @@ The chart can optionally be configured using the following parameters:
 | `maxMemory` | Maximum memory      | 24G               |
 | `existingDbSecret`  | Use MariaDB credentials from an existing secret. The secret has to contain the keys `databaseUsername` and `databasePassword`. Please refer to the [kubernetes documentation](https://kubernetes.io/docs/tasks/configmap-secret/managing-secret-using-kubectl/) for more information about how to create secrets | "" |
 | `externalDbConnectionUrl` | JDBC connection URL of an external MariaDB 10.x database. Requires the `existingDbSecret` parameter to be set | "" |
+| `registryUrl` | Container registry URL      | registry.averbis.com               |
 
 
 Specify each parameter using the `--set name=value` argument to `helm install` and `helm upgrade`  to overwrite the chart default values, for example:
 
 ```
-helm install hd averbis/health-discovery --set maxMemory=24G,existingDbSecret=my-secret,externalDbConnectionUrl=jdbc:mariadb://my-mariadb-host:3306/mydb?useMysqlMetadata=true
+helm install hd averbis/health-discovery --set maxMemory=24G,existingDbSecret=my-secret,externalDbConnectionUrl=jdbc:mariadb://my-mariadb-host:3306/mydb?useMysqlMetadata=true,
+registryUrl=my-registry-base-url
 ```
 
 NOTE: Once this chart is deployed, it is not possible to change the MariaDB access credentials, such as usernames or passwords, using Helm.
 
+NOTE: If using an alternative registry please make sure the structure of the image repositories is exactly as in the Averbis registry, i.e. currently:
+/health-discovery/health-discovery
+/mariadb/mariadb
+/solr/solr
+
 ### Exposing the Application
 Create a kubernetes `service` of type `loadBalancer` to access the application from outside the kubernetes cluster. Out of the box this only works
 with cloud providers like Google GKE or AWS EKS.

charts/health-discovery/templates/database-deployment.yaml

@@ -67,7 +67,7 @@ spec:
               value: 256m
             - name: innodb_log_file_size
               value: 256m
-          image: registry.averbis.com/mariadb/mariadb:9.4.0
+          image: {{ .Values.registryUrl }}/mariadb/mariadb:9.4.0
           name: database
           ports:
             - containerPort: 3306

charts/health-discovery/templates/health-discovery-deployment.yaml

@@ -65,7 +65,7 @@ spec:
               value: "solr"
             - name: SOLR_PORT
               value: "8983"
-          image: registry.averbis.com/health-discovery/health-discovery:7.1.0
+          image: {{ .Values.registryUrl }}/health-discovery/health-discovery:7.1.0
           livenessProbe:
             exec:
               command:

charts/health-discovery/templates/solr-deployment.yaml

@@ -37,7 +37,7 @@ spec:
               value: "8983"
             - name: TEXTANALYSIS_URL
               value: http://health-discovery:8080/health-discovery/rest
-          image: registry.averbis.com/solr/solr:9.4.0
+          image: {{ .Values.registryUrl }}/solr/solr:9.4.0
           livenessProbe:
             exec:
               command:

charts/health-discovery/values.yaml

@@ -3,3 +3,6 @@ maxMemory: "24G"
 
 # Use existing secret for MariaDB authentication parameters
 existingDbSecret: ""
+
+# Registry url to be used (default is Averbis registry)
+registryUrl: "registry.averbis.com"