Update configuration of PostgreSQL for CI to use /tmp directory #259
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.
Description
This PR updates the configuration of PostgreSQL for CI.
Recently, bitnami releases a new major version of helm chart for PostgreSQL.
https://github.com/bitnami/charts/tree/main/bitnami/postgresql#to-1500
It includes backward-incompatible updates and it causes error of PostgreSQL.
1. Security configurations
Some security configurations are changed to more strict.
Since the security configuration was made more strict, the container cannot create a new directory under the
/bitnami/
directory.So, I update to use
/tmp
directory instead of/bitnami/
.I think there is no problem if we use the
/tmp
directory because we use this PostgreSQL temporarily for CI. (I think for the production environment, using the/tmp
directory is not good.)2. Resources configurations
Before there is no resource limitations by default, but in the latest version, the bitnami helm chart set minimum resource configuration by default as follows.
Sometimes, this minimum resource limitation might cause OOM error as follows.
So, I added the configuration
primary.resourcesPreset: none
(the default value of previous version) explicitly.Please take a look!
Related issues and/or PRs
Some CI failed by the PostgreSQL failure.
Changes made
/tmp
directory for the data directory of PostgreSQL.Checklist
Additional notes (optional)
By using this new configuration, I was able to run the PostgreSQL in my local environment.
Release notes
N/A