Enable operator deploy via kustomize with out rbac-proxy

[rbounds]

Is your feature request related to a problem? Please describe.
Yes. I'd like to install the operator with out the rbac-proxy. The docs here seem to describe a situation where I should install via kustomize then clobber the freshly created resources with stuff from config. This feels at odds with out kustomize should work and kustomize does not allow one to remove the rbac-proxy side car.

Describe the solution you'd like
I think ideally I'd like to see the rbac-proxy sidecar and required configs to be their own patch that users can optionally include.

[NissesSenap]

@rbounds I don't think we will support this. It would force in to doing breaking changes on the current yaml that we supply.
It might be something worth considering in the 5.0 release #667

You can always follow the script in: https://github.com/grafana-operator/grafana-operator/blob/master/hack/release.sh to see how we the current yaml.
All you need to do is to edit https://github.com/grafana-operator/grafana-operator/blob/master/config/manager/kustomization.yaml and comment out - manager_auth_proxy_patch.yaml.

You can also use helm to deploy the operator if you want.
https://artifacthub.io/packages/helm/bitnami/grafana-operator

[rbounds]

Yeah. I saw the release.sh. I found more questions there than answers. Can you help me understand why you are using kustomize to build manifest then running kustomize create --autodetect ` on the result ? Why not just move all of the kustomize up the chain. Is this an attempt to reduce complexity for users?