[Bug] Endpoints for postgres operator on openshift cluster not created

[JoelGotsch]

Please, answer some short questions which should help us to understand your problem / question better?

• Used image: ghcr.io/zalando/postgres-operator-ui:v1.14.0
• Running on my bare metal openshift 4 cluster, following installation guide.
• Are you running Postgres Operator in production? no
• Type of issue: Bug

I followed the instructions to get the operator running on openshift. Hint: The Ingress also didn't work - had to create my own Route.

The operator service is running fine, but when creating a cluster, I get the following log lines in operator pod:

time="2025-04-13T19:46:02Z" level=info msg="ADD event has been queued" cluster-name=default/harbor-cluster pkg=controller worker=1
time="2025-04-13T19:46:02Z" level=info msg="creating a new Postgres cluster" cluster-name=default/harbor-cluster pkg=controller worker=1
time="2025-04-13T19:46:02Z" level=warning msg="cluster created failed: could not create master endpoint: could not create master endpoint: endpoints is forbidden: User \"system:serviceaccount:default:postgres-operator\" cannot create resource \"endpoints\" in API group \"\" in the namespace \"default\"" cluster-name=default/harbor-cluster pkg=cluster worker=1
time="2025-04-13T19:46:02Z" level=error msg="could not create cluster: could not create master endpoint: could not create master endpoint: endpoints is forbidden: User \"system:serviceaccount:default:postgres-operator\" cannot create resource \"endpoints\" in API group \"\" in the namespace \"default\"" cluster-name=default/harbor-cluster pkg=controller worker=1

I discovered: The rbac role for the openshift cluster seems to be lacking the rights to configure endpoints.
manifests/operator-service-account-rbac.yaml explicitly lists the endpoints, but manifests/operator-service-account-rbac-openshift.yaml is missing it.