Review PostgreSQL approach

[j08lue]

We are headed towards production deployments of eoapi-k8s.

We need to review and harden our approach for providing high-availability PostgreSQL

• PostgreSQL WAL directory consuming excessive storage and causing down time #181
• Document Postgresql RDS and HA (in k8s) Options #32

[knordstrom-muon]

My team is currently considering adopting eoapi-k8s and better documentation of using RDS would be very welcome! We are already invested in EKS + RDS for other tooling we deploy and prefer to pass in secrets using k8s secret names in the helm chart since our GitOps approach means we don't pass in plaintext secrets in the values. Is it currently possible to pass in the DB host, username, password etc as a structured k8s secret, and if not, would this be a big ask?

[pantierra]

@knordstrom-muon The use of eoapi-k8s with PostgreSQL on Amazon RDS is definitely a use case we want to support. This week, we are setting up a similar environment with a partner, and we'll be sure to document the process for eoapi-k8s. If needed, we'll also introduce any necessary changes. We'll keep you updated on the progress.

[knordstrom-muon]

Hi @pantierra, thanks for you quick response! That's good to know, we'll keep an eye out :)

[emmanuelmathot]

See #209 for a solution analysis

[knordstrom-muon]

Thanks @emmanuelmathot, that looks like a very complete solution!