Repository navigation
Is this project dead? #1131
Description
Activity
For the time being -- yes
Reacted by Jorge Solorzano, Phlegx Systems, Pierre Ozoux and Michel ZehnderThank you for the quick response. It is appreciated.
I would say no, because we still use it in production. But we use an internal fork from a branch. Let me sync with the team next week how we can rebase and maybe create another release. I wasn't involved in Spilo much in the past but I am willing to help.
Reacted by Kirill Petrov, Phlegx Systems, mbingel, theBNT, Timo , Vijay Dharap, Akash Gautam, Schmitt Christian, Pierre Ozoux, Marius Davidsen and 3 more@FxKu by chance any update on this?
Another +1 from me, I would love it if you guys could release a new version!
+1
Check out CloudNative PG. we converted all of our databases to use it. More features, and it has an auto-migration feature that works great if you are on Postgres 16. The Kubectl plugin lets you easily run psql from your terminal, and you can also use pgadmin4 using the plugin and a browser. Wish we had switched earlier.
CloudNative PG
with bugs like these: cloudnative-pg/cloudnative-pg#7407 no thanks. I will stay with patroni and It's not too hard to keep spilo up-to-date if you maintain a fork.
as long as new postgres versions do not break something I prefer to stay on software that has no stupid failure modesCheck out CloudNative PG. we converted all of our databases to use it. More features, and it has an auto-migration feature that works great if you are on Postgres 16. The Kubectl plugin lets you easily run psql from your terminal, and you can also use pgadmin4 using the plugin and a browser. Wish we had switched earlier.
In K8s of course I have migrated to CNPG for a long time and It was awesome
Checkout https://github.com/ParminCloud/Containers/tree/main/patroni we made a minimal and production-read image for the patroni and we are using it in production workloads when we are not in K8s
Hi @hughcapet, @FxKu, appreciate your input in this thread.
I'm curious why we're concluding the project is dead, if we're cutting new tags, as well as commits to main branch:
Can you help clarify the reasoning for this being considered dead given theres tags and main commits? Much appreciated
4.1-p1 released 4 days ago. Everything working fine. Seems alive to me.
Reacted by Sandor Szücs and Pierre Ozoux@Lebowski89 you mean this tag? https://github.com/zalando/spilo/tree/4.1-p1 - it says "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository." - what does this mean?
and will there be an official github release again?
@Lebowski89 you mean this tag? https://github.com/zalando/spilo/tree/4.1-p1 - it says "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository." - what does this mean?
and will there be an official github release again?
See:
Important: We encourage users to build the Docker images themselves from source code using the latest tags to benefit from ongoing improvements and fixes. The team continues to maintain the project and address issues, but does not make regular releases nor publishes latest Docker images.
Building the Docker image is the way to go forward if you want to stay up to date.
You'll see they're adding support for Postgres18 now: f332b91
Maybe they'll do another Docker image release for PG18.
There have been no products produced since last December (2024), and tickets are not getting attention.
Is this project dead?