There are a lot of Postgres operators. Wondering if a CNCF endorsement would place it as the “by default” operator to use. Could this reasoning be extended to other databases and stateful applications?
The project has just been submitted to the CNCF Sandbox, it hasn't yet been accepted. There's a lot of road to be done. If we get accepted, we'll be honoured to adapt and contribute to the project until incubation.
However, what is important here though is that this is the first operator for Postgres whose IP is now owned by a vendor neutral and openly governed community - or at least aims to be based on the public GOVERNANCE policies. We look upon the CNCF for principles and values.
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.
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.
The sandbox submission is not an endorsement from CNCF. It only demonstrates the willingness of the maintainer to create a community-driven, vendor-neutral software following the guidelines defined by CNCF.
Operators seem like a mandatory element for a lot of stateful applications to be working. MySQL, Kafka, OpenEBS, Cassandra… all need an operator to ensure day-2 operations.
I am just wondering if CNCF could provide signals that could help end users pick the right operator among the many out there. They could start with the projects they have in their landscape…
gbartolini|3 years ago
However, what is important here though is that this is the first operator for Postgres whose IP is now owned by a vendor neutral and openly governed community - or at least aims to be based on the public GOVERNANCE policies. We look upon the CNCF for principles and values.
This is our commitment.
sylvainkalache|3 years ago
That’s probably something the CNCF community should define.
gbartolini|3 years ago
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.
unknown|3 years ago
[deleted]
mnencia|3 years ago
Disclaimer: I'm one of the maintainers.
gbartolini|3 years ago
bipbip4242|3 years ago
I am just wondering if CNCF could provide signals that could help end users pick the right operator among the many out there. They could start with the projects they have in their landscape…