* [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
Add the ability to specify pod/deployment annotations through
`values.yml`.
I tested this works without any custom annotations, and also tested
specifying custom annotations and verifying they are included in the
existing pod/deployment.
* PostgreSQL metrics need the right username
If we use `POSTGERS_USER` = `sonar`, metrics go boom.
* Bump version
* Bumping PostgreSQL version
* Bumping PostgreSQL version
* PostgreSQL metrics need the right username
If we use `POSTGERS_USER` = `sonar`, metrics go boom.
* Bumping PostgreSQL version
* [stable/postgresql] standardize labels
* use "postgresql.name" as app label instead of "postgresql.fullname"
* match pods by two labels, release and app
* [stable/postgresql] bump version to 0.9.6
* [stable/postgresql] update notes
* [stable/postgresql] bump version to 0.11.0
* Fix for version comparison from strings to semver
See #3002 for more detail
* Include pre-releases in the semver ranges
This is important when testing against alpha and beta builds of
Kubernetes along with environments that use pre-releases to denote
things other than pre-releases (e.g., gke denotes the environment
with a pre-releases)
Add support for a fullnameOverride paramater to the PostgreSQL chart, matching
the pattern used by several other charts, as well as by the `helm create`
template chart.
* Increased probe timeout
When database is stoped brutally database can start with "FATAL: the database system is starting up".
Depending on the storage it may take more than 60 seconds to autofix and the POD will restart indefinitely.
* Increased version
* Update Chart.yaml
