document need for cluster-admin to run tests

[mhrivnak]

Feature Request

Users of OpenShift, and presumably other clusters as well, do not generally run as cluster-admin the way some developers do when using minikube or similar. When developing an operator on openshift, it would be helpful to have some documentation that provides guidance on the best or most appropriate way to ensure that the tests run with sufficient permission to create and remove the CRD.

[dhellmann]

I ended up with 1 extra step to add the cluster-admin ClusterRole to my user. It's possible a role with fewer privileges would work, too.

See https://github.com/metalkube/baremetal-operator#running-end-to-end-tests and https://github.com/metalkube/baremetal-operator/blob/master/test/e2e/role_binding.yaml

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[shawn-hurley]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[hasbro17]

/lifecycle frozen