Remove "hybrid" out of this operator's name

[rebbuh]

I suggest to remove the term "hybrid" out of this operator's name. In the cloud context, "hybrid" typically refers to a setup where some parts of the resources reside in a (public) cloud and other parts reside on on-premises solutions.

As far as I can see, this operator has nothing to do with this meaning of "hybrid", which is misleading. "Multi" is rather the term that seems to describe what this operator is for.

Therefore, I suggest to rename this operator, to e.g.
multi-cloud-postgresql-operator
k8s-postgresql-operator
postgresql-operator
...

[swoehrl-mw]

Hi @rebbuh. Thank you for your suggestion.

The primary intended purpose of this operator (and the others as well, I'll not post the same comment under all your issues) is IIoT platforms that consist of clusters running on-premise (as an edge or fog cluster in the factory) and in the cloud (different cloud providers) and we want to provide teams developing and deploying on these clusters with the same interface and experience regardless of wether the cluster is on-premise or in the cloud. Thus the "hybrid" in the name relates to clusters of the same platform being on-premise and in the cloud.

[rebbuh]

I understand your initial motivation, but I'm still not sure if that should be reflected in the operators' naming. Your goal is to spread the operator in der OSS community, and I guess that a majority of the future users does not have your primary intended purpose.

[swoehrl-mw]

You make a good point that the hybrid usecase is not the primary usecase for many people.
We will think about what to do with the naming of the operators.