ghost
commented
3 years ago Hi lissff, AKS bot here :wave: Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.
I might be just a bot, but I'm told my suggestions are normally quite good, as such: 1) If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster. 2) Please abide by the AKS repo Guidelines and Code of Conduct. 3) If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics? 4) Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS. 5) Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue. 6) If you have a question, do take a look at our AKS FAQ. We place the most common ones there!
raghulmsft
What happened:
For AAD integrated AKS, if user only had access to limited namespace, with role/rolebindings, .e.g.
_**apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: rolebinding-test-admin namespace: test roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: admin subjects:
User cannot use Kubernetes resource view in AKS portal to view/manage resources in his namespace. It only works for clusterRoles.
What you expected to happen: User should view/edit resources in his namespace in Kubernetes resource view in AKS portal
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version):