feat(deploy) add initContainer to wait for DB state #168
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
Kong can startup only if the DB schema is up to date. If Postgres is not up or the schema is not up to date, then Kong will fail to start, resulting in Pod restarts. This change will wait for Postgres to be up and migrations to finish running, avoiding restarts and failures in Kubernetes. There is currently no way to verify if DB state is at the correct version and hence we resort to a hack of actualling starting Kong and stopping it in the init container. With Kong >= 0.15.0, Kong will have a CLI command to check if migrations are up to date or not.
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.
Kong can startup only if the DB schema is up to date.
If Postgres is not up or the schema is not up to date, then Kong
will fail to start, resulting in Pod restarts.
This change will wait for Postgres to be up and migrations to finish
running, avoiding restarts and failures in Kubernetes.
There is currently no way to verify if DB state is at the correct
version and hence we resort to a hack of actualling starting Kong and
stopping it in the init container.
With Kong >= 0.15.0, Kong will have a CLI command to check if migrations
are up to date or not.