Filled out README files and added production config for wahlrecht

helm/wahlrecht/Chart.lock

@@ -1,6 +1,6 @@
 dependencies:
 - name: template
   repository: file://../template
-  version: 0.1.5
-digest: sha256:02ec98f8169a9fdd9155a9ffd790472f1ea0b1c1b1274ccaff10002aa42da2a7
-generated: "2023-08-20T20:04:03.22839+02:00"
+  version: 0.1.6
+digest: sha256:40131d6bbdde57f882dcdc958122f7a3553e3b71e6f24445a17dd12182b99bed
+generated: "2023-08-20T23:07:51.509297+02:00"

helm/wahlrecht/Chart.yaml

@@ -10,5 +10,5 @@ sources:
   - https://git.2martens.de/2martens/wahlrecht
 dependencies:
   - name: template
-    version: 0.1.5
+    version: 0.1.6
     repository: file://../template

helm/wahlrecht/README.md

@@ -3,7 +3,39 @@
 This chart installs the Wahlrecht API
 into the Kubernetes cluster.
 
-## Requirements
+## Configuration
 
-* running config server (host and port can be configured)
-* running Kafka (host and port can be configured)
+* by default, it expects a Spring Boot config server running inside the cluster, available under
+  http://configserver:8888/config
+  ```yaml
+  application:
+    configserver:
+      host: configserver
+      port: 8888
+      prefix: /config
+      scheme: http
+  ```
+* by default, it expects a Kafka running inside the cluster, available under
+  kafka:9092
+  ```yaml
+  application:
+    kafka:
+      host: kafka
+      port: 9092
+  ```
+* configure Keycloak
+  ```yaml
+  application:
+    keycloak:
+      url: https://yourKeycloak
+      realm: yourRealm
+  ```
+* configure secrets (the application expects these values to be set)
+  ```yaml
+  secrets:
+    MONGODB_CONNECTION_STRING: mongoDBConnectionString
+    CLIENT_SECRET: keycloakClientSecret
+  ```
+  Should you want to use, for example, an external secret provider,
+  then you are currently out of luck. The chart does not support that,
+  yet.

helm/wahlrecht/environments/production.yaml

@@ -0,0 +1,2 @@
+image:
+  tag: 0.2.8