Extended Readme.md

Author: etoensfeldt

README.md

@@ -41,9 +41,13 @@
 | `project.auth.ssh_key`                   | SSH private key for accessing the git repository. Overridden by ssh_secret, Optional.                  | `""`                   |
 | `project.auth.safe_key`                  | If false, the ssh key won't be saved on the cluster and will be deleted from the cluster.              | `true`                 |
 | `containerHistoryLimit`                  | The size of the history of deployments kept for potential rollbacks.                                   | `10`                   |
+| `mongodb.deploy`                         | If false, the mongodb container wont be deployed. Useful when using integrated db of opcrouter/runtime.| `true`                 |
 | `mongodb.auth.dbRootPassword`            | Root password for the mongodb. Will override autogenerated or existing one in secret.                  | `""`                   |
 | `mongodb.auth.dbReplicaKeySet`           | Replica set key for the mongodb. Will override autogenerated or existing one in secret.                | `""`                   |
 
+### WARNING: MongoDB root password and replica key set
+
+When using the mongodb container, keep in mind that that the root password and replica key set can only be set once, as upon initial declaration they are stored in a persistent volume. This may be an issue when using automatically deploying the chart using ArgoCD or Flux, as automatic redeployments can cause the root password to be regenerated when not having set static values for them in the values.yaml. This however will only make the database inaccessible to the opc router, as it will use the new passwords, though the mongodb still uses the old initial passwords. Thus it is highly recommended to set mongodb.auth.dbRootPassword and mongodb.auth.dbReplicaKeySet when not manually deploying the chart for testing purposes.
 
 ### Add extra environment variables