Merge pull request #40 from bbkz/postgres

Postgres update docs / no version bump

README.md

@@ -193,6 +193,8 @@ The following settings are declared in the groundhog2k Helm charts.
 
 #### PostgreSQL
 
+wger-app requires for the django database migrations the superuser privileges, so we grant the `postgres.userDatabase.name` `SUPERUSER` with a `postgres.extraScripts`.
+
 | Name | Description | Type | Default Value |
 |------|-------------|------|---------------|
 | `postgres.enabled` | Enable the PostgreSQL chart | Boolean | `True` |
@@ -201,6 +203,7 @@ The following settings are declared in the groundhog2k Helm charts.
 | `postgres.userDatabase.name` | Database name to use for wger | String | `wger` |
 | `postgres.userDatabase.user` | Username to use for wger | String | `wger` |
 | `postgres.userDatabase.password` | Password for wger user | String | `wger` |
+| `postgres.extraScripts` | A configmap used to grant privileges | String | `wger-pg-init` |
 | `postgres.service.port` | PostreSQL service port | Integer | `5432` |
 | `postgres.storage.persistentVolumeClaimName` | PVC name when existing storage volume should be used | String | `Nil` |
 | `postgres.storage.requestedSize` | Size for new PVC, when no existing PVC is used | Integer | `8Gi` |

RELEASENOTES.md

@@ -12,7 +12,7 @@ The superuser was named `wger`, but this seems to lead to a error in the postgre
 FATAL:  role "postgres" does not exist
 ```
 
-So you need to manually add a `postgres` superuser:
+So if you are upgrading, you need to manually add a `postgres` superuser:
 
 ```bash
 kubectl -n wger exec -ti wger-postgres-0 -- bash
@@ -21,7 +21,7 @@ psql -U wger
 CREATE ROLE postgres WITH LOGIN SUPERUSER PASSWORD 'postgres';
 ```
 
-As well set the settings in your `values.yaml`:
+As well set the following settings in your `values.yaml`:
 
 ```yaml
 postgres:

charts/wger/templates/configmap.yaml

@@ -50,5 +50,5 @@ apiVersion: v1
 metadata:
   name: wger-pg-init
 data:
-  grantSuperuser.sql: |
+  40-grantSuperuser.sql: |
     ALTER USER {{ .Values.postgres.userDatabase.name }} WITH SUPERUSER;

charts/wger/values.yaml

@@ -116,15 +116,18 @@ postgres:
   # Note: keep these variables present as the wger chart uses them for the deployment
   # the superuser and user settings will be saved into a secret
   enabled: true
-  # after the first installation the superuser and userDatabase settings will be ignored
-  # they will be taken from the secret
+  # changes to the superuser and userDatabase passwords will update
+  # the secret where they are save in
   settings:
     superuser: postgres
     superuserPassword: postgres
   userDatabase:
     name: wger
     user: wger
     password: wger
+  # the user from the user database will be turned into a superuser
+  # some database migration in django requires this
+  # otherwise it was not able to create the database
   extraScripts: wger-pg-init
   service:
     port: 5432