Azure
[Feature] Enabling RBAC on an existing cluster created without RBAC
Is your feature request related to a problem? Please describe. Currently, it is not possible to enable RBAC on a cluster created without RBAC. Since recreating cluster with RBAC is not practical all the time, a feature for enabling RBAC on an existing cluster will be helpful.
Describe the solution you'd like A feature to enable RBAC on an existing cluster without RBAC
Hi, have you tried changing it from the "cluster configurations" side menu?
Are you asking about enabling Azure RBAC on an existing cluster? If so, you can find the instructions here: https://learn.microsoft.com/en-us/azure/aks/manage-azure-rbac#integrate-azure-rbac-into-an-existing-cluster
I see that it's now possible to enable Azure RBAC for Kubernetes in an existing cluster: https://learn.microsoft.com/en-us/azure/aks/manage-azure-rbac#integrate-azure-rbac-into-an-existing-cluster
I have a few questions:
- Does enabling Azure RBAC work in clusters where Kubernetes RBAC is not enabled?
- Does enabling Azure RBAC also enable Kubernetes RBAC? Is it possible to enable Azure RBAC and then disable it in order to enable Kubernetes RBAC?
- Is there any priority for getting Kubernetes RBAC enabled in clusters created before
2020-03-01? Any idea when that will be possible? - Are there any other recommended workarounds for this?
Thanks!
Hello! Any chance we can get an update on this in 2025?
It would be nice to know if this is going to happen or just close the issue as won't fix if not so that organizations that rely on Microsoft Azure could make business decisions about how to deal with this situation.
Thanks so much! ☺️
![microsoft-github-policy-service[bot] avatar](https://avatars.githubusercontent.com/in/95686?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs within 7 days of this comment. @shashankbarsin
This issue will now be closed because it hasn't had any activity for 7 days after stale. @EJASKHAN feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.