Make Auto Deploy databases persistent

We need to make databases used in Auto Deploy persistent. Currently they are ephemeral, so a restart of the postgres pod will wipe the data. It's possible this is desired for review apps, but it's certainly not desired for production.

Links

• Docs: https://docs.gitlab.com/ee/ci/autodeploy/index.html#postgresql-database-support

Documentation blurb

Auto Deploy is already able to run a database instance, so you can benefit of its automatic availability for your application. Since 9.4, this instance is ephemeral and recreated every time the pod is restarted. With GitLab 9.5 we're introducing persistence for databases, making then impossible to use this feature in production environments.

mentioned in issue #32829 (closed)

@ayufan Sounds like this is done with 9.3 helm chart changes. Correct?

added Deliverable label

marked this issue as related to #32829 (closed)

changed milestone to %10.0

assigned to @ayufan and @nolith

added In review label

mentioned in merge request gitlab-ci-yml!88 (merged)

Closed by https://gitlab.com/gitlab-org/gitlab-ci-yml/merge_requests/88.

closed

@bikebilly Since this no longer applies to Auto Deploy, it's not worth blogging from that perspective, but it might be work to add a small note to the release post about all the improvements to Auto Deploy that are now in Auto DevOps. e.g. persistent databases and helm charts.