Creating the Operator from config/openshift doesn't create serviceaccount "controller"

[guhilling]

Tried to deploy the operator either from "https://github.com/metallb/metallb-operator/config/openshift?ref=" (main or 0.14.0) the serviceaccount "controller" is not being created.
It's referred to from the deployment "controller" and "metallb-operator-webhook-server".
When using the OpenShift operatorhub this serviceaccount is created automatically.
Serviceaccount "speaker" is also missing and won't be created automatically

[fedepaol]

I am tempted to say that when installing on openshift, one should use the official way to deploy the operator, but on the other hand this can be useful for quick validation of what's on upstream before it's officially delivered.

[guhilling]

This also applies to OKD where you don't have the option to use the "official spin" as there is none.

[snehring]

if you do KUSTOMIZE_DEPLOY_DIR=config/openshift make set-namespace-openshift bin then apply the resulting bin/metallb-operator.yaml the operator seems to deploy successfully on OKD. The openshift kustomize alone doesn't include some of the rbac stuff. Not sure if that's by design or not, I don't know a ton about kustomize and found this issue when I ran into the same problem with OKD.