Is it still maintained ?

[throrin19]

Is the project still on track? Would it be only this one but also timescaledb-ha?

It's been several weeks or even months that problems with Patroni are present but nothing seems to change, as well as several configuration questions which are not answered due to validation problems with the charts configurations.

This naturally leads to this question: Is the project still active? Or is it "paused" to favor timescaledb Cloud over self-hosted?

[sumerman]

Apologies, I had my wires crossed and replied as if you were asking about promscale.

[cryptobench]

Bump. Following this

[fungiboletus]

Bump. Following this

You can also add a thumb up on the first message and click the "subscribe" button 🙂

[github-actions]

This issue went stale because it was not updated in a month. Please consider updating it to improve the quality of the project.

[throrin19]

I think the github bot comment respond for us.

Can you confirm @feikesteenbergen ?

[github-actions]

This issue went stale because it was not updated in a month. Please consider updating it to improve the quality of the project.

[github-actions]

This issue went stale because it was not updated in a month. Please consider updating it to improve the quality of the project.

[mindrunner]

It is hardly maintained. PR reviews take ages and (as of my experience) only happen when you run after it. A quite important fix for something I filed about half a year ago is still not released to the helm repos (even though it was already merged to master weeks ago).

[github-actions]

This issue went stale because it was not updated in a month. Please consider updating it to improve the quality of the project.

[timclifford]

Is someone able to give an update on the situation from the maintainers? Just so people can get a measure and plan a little better

[github-actions]

This issue went stale because it was not updated in a month. Please consider updating it to improve the quality of the project.

[mindrunner]

^^

[github-actions]

This issue went stale because it was not updated in a month. Please consider updating it to improve the quality of the project.

[Snazzie]

bad bot

[github-actions]

This issue went stale because it was not updated in a month. Please consider updating it to improve the quality of the project.

[Snazzie]

bad bot

[tobywinnow]

Is it time for us to fork this and create a community managed helm chart?
The lack of engagement with PRs seems quite deliberate here.

[mindrunner]

[mindrunner]

I have repeatedly offered my assistance to the project and inquired about the possibility of becoming an official maintainer. At that time, I was already managing my own fork, which included patches that were not merged into the main project. Unfortunately, this initiative did not succeed, and eventually, our communication diminished.

Currently, I am no longer working full-time with timescaledb, which limits my ability to lead such a project. An actively maintained Helm chart is essential for running this in a production environment, particularly because this chart is complex and still has several issues that need resolution.

[github-actions]

This issue went stale because it was not updated in a month. Please consider updating it to improve the quality of the project.

[throrin19]

Bad bot....