helm-charts
helm-charts copied to clipboard
add_data_node
2020-10-22T01:55:48.722480169Z timscaledb-timescaledb-data-0.timscaledb-timescaledb-data:5432 - accepting connections
2020-10-22T01:55:48.748617533Z You are now connected to database "postgres" as user "postgres".
2020-10-22T01:55:48.771230739Z You are now connected to database "postgres" as user "postgres".
2020-10-22T01:55:48.771327219Z SELECT *
2020-10-22T01:55:48.771352966Z FROM add_data_node('timscaledb-timescaledb-data-0'::name, host => 'timscaledb-timescaledb-data-0.timscaledb-timescaledb-data', if_not_exists => true)
2020-10-22T01:55:48.773014359Z psql:
Could you give some context to what you're doing? Which Docker Image do you use? What is in your values.yaml
?
We have a template that we'd like you to fill out when raising an issue here:
https://github.com/timescale/timescaledb-kubernetes/issues/new?assignees=&labels=&template=bug_report.md&title=%5BISSUE%5D
This is to ensure we can more quickly understand what you're trying to accomplish and what the context is. In general, that will speed up a resolution to your issues.
We are sorry to say that multinode helm chart is deprecated and not supported anymore. If you want to see this chart supported then we are looking for community maintainers - https://github.com/timescale/helm-charts/tree/master/charts/timescaledb-multinode#call-for-maintainers
I am closing this issue as TimescaleDB-Multinode helm chart is no longer maintained and deprecated. We are looking for potential community maintainers who could help us in getting that helm chart working again. If you wish to become a maintainer, please contact us on slack.
Keep in mind that TimescaleDB is not and will not be dropping multinode setup. Deprecation is only about helm chart.