* [stable/postgresql] Allow including gzip files as initdb scripts
Signed-off-by: juan131 <juan@bitnami.com>
* Increasing Prerequisites on README.md
Signed-off-by: juan131 <juan@bitnami.com>
* Only create cm when there are init scripts
Signed-off-by: juan131 <juan@bitnami.com>
* Only use init cm when there are init scripts
Signed-off-by: juan131 <juan@bitnami.com>
* minor fixes
Signed-off-by: juan131 <juan@bitnami.com>
* [stable/postgresql] Allow mounting secrets as files
Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
* Add mounting logic to the metrics container
Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
* Lint
Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
* When persistence is disabled the empty volume gets added in the wrong spot.
It ends up generating yaml like this:
updateStrategy:
type: RollingUpdate
- name: data
emptyDir: {}
Signed-off-by: Chris Malloy <chris.malloy@mathresources.com>
* Bumped version.
Signed-off-by: Chris Malloy <chris.malloy@mathresources.com>
Signed-off-by: Gabriel Nicolas Avellaneda <avellaneda.gabriel@gmail.com>
Do not create a Deployment for the psql client to test connectivity with PostgreSQL
Signed-off-by: Gabriel Nicolas Avellaneda <avellaneda.gabriel@gmail.com>
Fixed command line for test client to add namespace to be able to make connection to the deployed PostgreSQL
Signed-off-by: Gabriel Nicolas Avellaneda <avellaneda.gabriel@gmail.com>
Bump chart version
Signed-off-by: Gabriel Nicolas Avellaneda <avellaneda.gabriel@gmail.com>
What does this commit/MR/PR do?
- Remove extra lines in secrets.yaml
Why is this commit/MR/PR needed?
- There should be one key/pair per line
Signed-off-by: Stephen Moloney <stephen@stephenmoloney.com>
* [stable/postgresql] Support different affinities for master & slaves
Signed-off-by: tompizmor <tompizmor@gmail.com>
* Add note to README and obey fullnameOverride
Signed-off-by: tompizmor <tompizmor@gmail.com>
* Added debugging flags to master node
Signed-off-by: Joao C Costa <joaocc-dev@live.com>
* Annotation style consistent with master
Signed-off-by: Joao C Costa <joaocc-dev@live.com>
* Added terminationGracePeriod spec to slave nodes
Signed-off-by: Joao C Costa <joaocc-dev@live.com>
* Bump chart version
Signed-off-by: Joao C Costa <joaocc-dev@live.com>
* fixing env vars value - helm requires them to be strings
Signed-off-by: Joao C Costa <joaocc-dev@live.com>
* [stable/postgresql] bump chart version
Signed-off-by: Joao C Costa <joaocc-dev@live.com>
* [stable/postgresql] Add ability to give postgresql or pg_hba configuration from parameter.
Signed-off-by: Cédric de Saint Martin <cdesaintmartin@wiremind.fr>
* [stable/postgresql] Add ability to give initdb scripts from parameter.
Signed-off-by: Cédric de Saint Martin <cdesaintmartin@wiremind.fr>
* [stable/postgresql] Fix NOTES.txt render error when service type is LoadBalancer
Signed-off-by: tompizmor <tompizmor@gmail.com>
* Delete wrong line
Signed-off-by: tompizmor <tompizmor@gmail.com>
This commit enables the user to specify additional environment
variables in the postgres chart.
This is especially important for custom Postgres images which might
have different environment variables for different options or for
enabling additional features.
Furthermore versions have been updated:
- Chart version has been set to 1.0.0, as this is a stable chart
Signed-off-by: Bojan Čekrlić <bojan@cekrlic.com>
"-extend.query-path" is invalid argument to postgres_exporter since
0.4.x version due to cli library update (ref:
https://github.com/wrouesnel/postgres_exporter/issues/147)
Currently, as a result of invalid argument, metrics container fails
to start.
This commit fixes the issue by replacing broken command line argument
with the corresponding environment variable, as they are more consistent.
Signed-off-by: Igor Zibarev <zibarev.i@gmail.com>
Currently, custom metrics for "metrics" image of postgresql pod are
broken. This is because the volume is specified incorrectly. Thus, the
deployment ends up creating `emptyDir: {}` volume instead of `configMap`
one.
This commit fixes it.
Signed-off-by: Igor Zibarev <zibarev.i@gmail.com>
* postgresql: Remove myself from maintainers
I have not been responsive to requests in the past year. In order avoid frustrations with future PRs I withdraw myself from the list.
* bump chart version
* [postgresql] Set update strategy to Recreate.
We NEVER want two different postgres instances to be up at the same time using the same database files, or corruption can occur.
At the cost of having a few seconds of downtime at upgrade time.
* Update Chart.yaml
* Adding values for liveness & readiness probe thresholds
* Postgresql: Upping chart version
* Removing use of default as it is redundant
* Incrementing chart version as it seems someone beat me to it
* Update Chart.yaml
