Skip to content

Inaccurate statement in the docs for server ClusterRole and ClusterRoleBinding  #310

@angabini

Description

@angabini

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions