* Postgres exporter authenticate to postgres db primary
The postgres exporter is monitoring all the dbs in the postgresql cluster.
The postgres exporter will query by default all the dbs through the db of the username you are using for instance when you use "postgres" user the exporter will query all the dbs through db postgres, when you use "test" user the exporter will query all the dbs through db test.
You able to assign the db you want to query through the URI in the postgres exporter.
Lets say you are using user "test" and there is no db "test", the exporter will not work and the connection will fail.
When using a custom username for the postgres and using the URI in the postgres exporter that currently set, the connection will fall because it will search for a db with that name that might exist or not.
Postgres always have "postgres" db for its internal uses and this helm chart always deploys admin user.
Conclustion: we can use in the URI the postgres db because we are admin and the postgres db exist
Signed-off-by: Koren Peretz <62677694+KorenP1@users.noreply.github.com>
* Postgres exporter primary URI fix
The postgres exporter is monitoring all the dbs in the postgresql cluster.
The postgres exporter will query by default all the dbs through the db of the username you are using for instance when you use "postgres" user the exporter will query all the dbs through db postgres, when you use "test" user the exporter will query all the dbs through db test.
You able to assign the db you want to query through the URI in the postgres exporter.
Lets say you are using user "test" and there is no db "test", the exporter will not work and the connection will fail.
When using a custom username for the postgres and using the URI in the postgres exporter that currently set, the connection will fall because it will search for a db with that name that might exist or not.
Postgres always have "postgres" db for its internal uses and this helm chart always deploys admin user.
Conclustion: we can use in the URI the postgres db because we are admin and the postgres db exist
Signed-off-by: Koren Peretz <62677694+KorenP1@users.noreply.github.com>
* Update Chart.yaml
ApiVersion for pipeline
Signed-off-by: Koren Peretz <62677694+KorenP1@users.noreply.github.com>
* Update CHANGELOG.md
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
* Update Chart.yaml
Signed-off-by: Koren Peretz <62677694+KorenP1@users.noreply.github.com>
* Update CHANGELOG.md
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
* Update CHANGELOG.md
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
* Update CHANGELOG.md
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
---------
Signed-off-by: Koren Peretz <62677694+KorenP1@users.noreply.github.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
* postgres exporter monitor all databases
Currently there is no option to monitor all databases with postgres exporter without mentioning the databases names and creating them in the init scripts. (.Values.auth.database). Postgres Exporter does let this feature work if you dont mention any databases in the URI and that is why i think the required statement is not correct so i removed it.
Signed-off-by: Koren Peretz <62677694+KorenP1@users.noreply.github.com>
* Update Chart.yaml
Adding Chart.yaml version bump to pass tests
Signed-off-by: Koren Peretz <62677694+KorenP1@users.noreply.github.com>
* Update CHANGELOG.md
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
* Update CHANGELOG.md
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
* Update statefulset.yaml
Looks like there is no usage of the DB NAME part in the DATA_SOURCE_URI environment variable which means there is no need for the $database part, the postgres exporter always monitoring all the dbs, also if created after the initialization and not mentioned in the DATA_SOURCE_URI env var.
In conclusion the PR is for two reasons.
1: making DATA_SOURCE_URI env var more "right" and related to what it actually does
2: More importantly, removing the required statement in the $database helm variable assignment in order for users to be able to deploy the postgres exporter although not assigning .Values.auth.database variable for the db creation in the initialization of the postgres
Signed-off-by: Koren Peretz <62677694+KorenP1@users.noreply.github.com>
* Update statefulset.yaml
Signed-off-by: Koren Peretz <62677694+KorenP1@users.noreply.github.com>
* Update CHANGELOG.md
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
---------
Signed-off-by: Koren Peretz <62677694+KorenP1@users.noreply.github.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
* [bitnami/*] chore: 👷 Add tag and changelog support
Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>
* perf: ⚡ Avoid fetching the index branch
Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>
* chore: 🔧 Do not scan CHANGELOG.md files
Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>
* chore: 🙈 Update .helmignore files
Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>
* refactor: ♻️ Separate push-tag section
Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>
---------
Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>
* [bitnami/postgresql] fix: 🐛 Always mount data directory
Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>
* Update Chart.yaml
Signed-off-by: Javier J. Salmerón-García <jsalmeron@vmware.com>
---------
Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>
Signed-off-by: Javier J. Salmerón-García <jsalmeron@vmware.com>
