Helm charts - allow external db to be configured
Improve the helm charts so a external db can be specified instead of bringing up a new database within the cluster.
This is what we consider to be a required for currently using the template in a production environment. As the included postgres dependency is not current 'safe'.
My reasoning being:
- Performance is poor unless you can get the db container to stay on a node with fast access to it's storage. Having the DB storage on something like NFS has been sometimes painful during demos.
- Cannot be scaled using replicas
- Risk of the container dying (perhaps even being killed due to a failed healthcheck) and causing data corruption are currently higher than I think is acceptable for a production deployment
Allowing the configuration of a external DB, whether it is another better cloud native DB in the cluster, or something outside the cluster, should result in our gitlab chart being able to be used in a production environment.
Steps:
-
Update gitlab chart in charts.gitlab.io -
Create PR for curated chart
cc\ @JobV @markpundsack