Provide RBAC manifests about operator-sdk HOT 8 CLOSED

@hasbro17 should those be auto-generated and managed by operator-sdk?

from operator-sdk.

Yeah I was thinking they could be generated by operator-sdk in deploy/rbac.yaml. And then the user just creates them before creating deploy/operator.yaml

from operator-sdk.

kk, maybe operator-sdk new can create both deploy/rbac.yaml and deploy/crd.yaml. then let operator-sdk build to create operator.yaml.

from operator-sdk.

Yeah rbac.yaml and crd.yaml only need to be generated once(unlike operator.yaml which has the image field) so we can do them as part of operator-sdk new.

from operator-sdk.

alright. let's just implement what we have discussed

from operator-sdk.

@fanminshi please update here once you have confirmed if RBAC setup is necessary for default or any other namespace on Minikube.
We'll decide whether or not RBAC setup is strictly required in the README after that.

from operator-sdk.

whether or not RBAC setup is strictly required in the README

If RBAC setup is strictly required on Minikube, SDK had better generate them for users.

from operator-sdk.

Seems like minikube requires RBAC setup. So the SDK will now generate deploy/rbac.yaml whose contents are as I've listed in my first comment.
And then we need to add a step in the README to tell the user to create deploy/rbac.yaml before creating deploy/operator.yaml.

from operator-sdk.