rbac.yaml

# This file is exclusively to be used when you are using Microsoft Entra ID direct assignment for Kubertnetes RBAC 
# and NOT when you are using Azure RBAC as your Kubernetes RBAC backing store.
#
#  Map k8s user facing namespace roles to Microsoft Entra groups: https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles
#apiVersion: rbac.authorization.k8s.io/v1
#kind: RoleBinding
#metadata:
#  name: namespace-admin
#  namespace: a0008
#roleRef:
#  apiGroup: rbac.authorization.k8s.io
#  kind: ClusterRole
#  name: admin
#subjects:
#  - kind: Group
#    name: <replace-with-a-microsoft-entra-group-object-id-for-this-namespace-role-binding>
#---
#apiVersion: rbac.authorization.k8s.io/v1
#kind: RoleBinding
#metadata:
#  name: namespace-editor
#  namespace: a0008
#roleRef:
#  apiGroup: rbac.authorization.k8s.io
#  kind: ClusterRole
#  name: edit
#subjects:
#  - kind: Group
#    name: <replace-with-a-microsoft-entra-group-object-id-for-this-namespace-role-binding>
#---
#apiVersion: rbac.authorization.k8s.io/v1
#kind: RoleBinding
#metadata:
#  name: namespace-viewer
#  namespace: a0008
#roleRef:
#  apiGroup: rbac.authorization.k8s.io
#  kind: ClusterRole
#  name: view
#subjects:
#  - kind: Group
#    name: <replace-with-a-microsoft-entra-group-object-id-for-this-namespace-role-binding>