TimescaleDb

[MarkCupitt]

Name and Version

Potential New Chart

What is the problem this feature will solve?

TmescaleDb is a postgresql based Time Series Db. It has growing support and a community-developed Helm Chart that works, but is not getting any maintenance

https://github.com/timescale/helm-charts/tree/main/charts/timescaledb-single

What is the feature you are proposing to solve the problem?

We would love to see it included in the Bitnami Stack. I have deployed it, and the chart as it stands, works fine.

Ther distributed version is now deprecated, so there is only the single version to worry about

What alternatives have you considered?

Turn the hem chart into parsed yaml and do it myself .. but would be happy to test out a Bitnami Version if you guys decide to include it in your excellent offerings

[carrodher]

Thanks for your suggestion!

We will check it internally and evaluate the feasibility of adding this new product to the catalog; due to limited resources, this process could take some time. In the meantime and to prevent the stale bot from closing this issue, we will add the 'on-hold' label.

[MarkCupitt]

thankyou ...

On Mon, 8 Jan 2024, 5:37 pm Carlos Rodríguez Hernández, < @.***> wrote:

Thanks for your suggestion!

We will check it internally and evaluate the feasibility of adding this new product to the catalog; due to limited resources, this process could take some time. In the meantime and to prevent the stale bot from closing this issue, we will add the 'on-hold' label.

— Reply to this email directly, view it on GitHub https://github.com/bitnami/charts/issues/21880#issuecomment-1880654895, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJ7RUB6VR7VLR22BP4EOALYNO44FAVCNFSM6AAAAABBRCLZJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQGY2TIOBZGU . You are receiving this because you authored the thread.Message ID: @.***>

[zivyankelevitz]

thank you both

[zivyankelevitz]

currently bitnami has a postgreSQL helm chart for cluster, but it is using different technologies than this timescale chart(does not use patroni for example), and do not have the nice capability related with automatic backups using pgBackrest tool/wal archiving. so basically for many cluster failure it will need manual intervention to fix the failed node(s)

[MarkCupitt]

Some additional tickets for issues I have resolved with timescaledb, to help you out (for your reference) are at

https://github.com/timescale/timescaledb-docker-ha/issues/435

and

https://github.com/timescale/helm-charts/issues/641 https://github.com/timescale/helm-charts/issues/642 https://github.com/timescale/helm-charts/issues/639

[jamessewell]

This is great. I'd love to work together to get the helm chart into your stack (I run Developer Advocacy @ Timescale)

[theblinkingusb]

This would be useful for going forward. I'd be able to help out as well with testing or maybe in the chart migration as well with some guidance. I currently run the legacy helm chart that has been archived by the Timescale team.

[berlincount]

Considering that TimescaleDB primarily comes as an extension to PostgreSQL - would maybe improving the Extension mechanism for the postgresql helm chart be the quickest win?

Maybe even just selecting a postgresql image with TimescaleDB already integrated would suffice?

[zivyankelevitz]

the current bitnami postgreSQL helm is using different technologies than this timescale chart(does not use patroni for example), and do not have the nice capability related with automatic backups using pgBackrest tool/wal archiving. so basically for many cluster failure it will need manual intervention to fix the failed node(s) do tou think this is something you can support on Bitnami? patroni + pgbackrest, the same way it is done in the Timescale chart?

[jamessewell]

Just popping up again to offer help from the Timescale side if needed