Kubernetes cluster > Add ability to change the RBAC-enabled setting

Problem to solve

If you create a cluster and do not enable RBAC, there is no way to enable it later, and vice-versa.

Further details

(Include use cases, benefits, and/or goals)

Proposal

Allow the user to change the RBAC-enabled setting via the cluster detail UI and automatically create the necessary RBAC-related resources.

• What happens when an RBAC-enabled cluster disables RBAC ? Will Helm Tiller need to be reconfigured ?

What does success look like, and how can we measure that?

(If no way to measure success, link to an issue that will implement a way to measure this)

Links / references

• https://docs.gitlab.com/ee/user/project/clusters/index.html#role-based-access-control-rbac