[sylvainkalache]

There is a need to standardize operators. Not only to streamline their usage, but also to ensure quality or at least give the community guidelines on what are the best practices to follow when building or using an operator.

That’s probably something the CNCF community should define.

[gbartolini]

There's definitely commonalities between operators for databases, not only with the same engine, but also different ones and similar primary/standby architecture.

I agree this is something we could somehow work together as a standard kind of spec, but probably we are still at an early stage of the process. My 2 cents.

[hodgesrm]

Agree. Monitoring is a great example. Every DBMS server needs monitoring and it should be exportable to Prometheus. But the commonality ends pretty much ends there, at least in my experience. That's just single instances, too, not complex clusters.

[gbartolini]

That's another good example of why CNCF is important, as in that ecosystem live technologies that are becoming standard for everything related to infrastructure, including monitoring and alerting. Prometheus is an example, Open Telemetry is another one. When you are able to "interface" with one of these components, you've done your integration job.

From a Postgres standpoint, IMO, it is also important the concept of cluster - as that's what applications connect too - the operator hides the underlying complexity of managing the single instances. And .. also important monitoring sets of clusters from an infrastructure management PoV.