Abort Metacat Startup if PostgreSQL not accessible (k8s only)

Open artntek opened this issue 2 years ago • 1 comments

If metacat is running in a container (see env var METACAT_IN_K8S), check on startup that PostgreSQL database is running and accessible. If not, abort startup (see #1631).

If legacy deployment (i.e. non-containerized), we MUST allow startup to happen without postgres available, since the operator will then be prompted for connection credentials via the admin page

Jul 24 '23 20:07 artntek

Re-assess this. May not be best practice for k8s. Better to fail readiness probe until PG becomes available??

May 09 '24 01:05 artntek