The doc states that:
|
To allow the server to read and write to this configmap, a ClusterRole must be created that confers the appropriate entitlements to Kubernetes RBAC, and that ClusterRoleBinding must be associated with the service account created in the previous step. |
Though, the rule in ClusterRole definitions is:
- apiGroups: ["authentication.k8s.io"]
resources: ["tokenreviews"]
verbs: ["create"]
Which seems to have nothing to do with configmaps.
I believe the statement applies to Role/RoleBinding. So, the doc should be updated and possibly needs and addition for why ClusterRole /ClusterRoleBinding are needed.