[kmarc]

I used this in the past. Helped a lot with provisioning micro-pg-clusters.

But honestly, the project always felt like a one-man-show, some (realy great) dev had a working set of scripts and kubernetized / operatorized it, but the whole thing feels hacky as hell.

I'd still give a try if I ever needed postgresql again, but I would also know that I need to implement (again) my set of scripts and hacks on top of it.

[gbartolini]

Maintainer of CloudNativePG here.

Back then, we evaluated Crunchy Operator's source code. Being primarily imperative and using an external tool for failover, where the two main reasons we decided to start a new project in 2019 which was entirely declarative and purely based on the Kubernetes API server for cluster status. Such project was released open source last April under the name CloudNativePG and hopefully it will enter the CNCF Sandbox soon (fingers crossed).

[smartbit]

> the whole thing feels hacky as hell

Couldn’t agree with you more, especially if you’re used to the quality of strimzi.

[kmarc]

Did we work on the same project? I was also responsible to integrate strimzi (redhat amq streams) and gosh that's a quality piece of software!