geoserver: wait for DB and DB user to be available #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Waiting just for Postgres to be accepting TCP connections is not enough. The Postgres service is slow to set up during the first deploy. GeoFence would fail to create its tables (as the DB is not ready yet), and stay broken instead of crashing or trying again. Note that an image including psql is necessary.
randomorder
requested changes
Jun 27, 2024
charts/geonode/values.yaml
Outdated
| @@ -348,9 +348,9 @@ geoserver: | |||
| container_name: geoserver-wait-for-db | |||
| image: | |||
| # init container image | |||
| name: jwilder/dockerize | |||
| name: governmentpaas/psql | |||
There was a problem hiding this comment.
can we use an official image instead?
There was a problem hiding this comment.
I wish, but which image is an official image with just psql? I don't want a big image just for psql.
There was a problem hiding this comment.
evantually the same used by the zalando cluster if available in the values file
There was a problem hiding this comment.
Ok. My latest commit uses postgres:16-alpine.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Waiting just for Postgres to be accepting TCP connections is not enough.
The Postgres service is slow to set up during the first deploy. GeoFence would fail to create its tables (as the DB is not ready yet), and stay broken instead of crashing or trying again.
Note that an image including psql is necessary. Here I'm using
governmentpaas/psqlbut maybe we'll want to create our own.