📖 docs: add missing RBAC bindings / rules#50
Conversation
Signed-off-by: Daniel Kraus <daniel.kraus@kubermatic.com>
|
Hi @dakraus. Thanks for your PR. I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/approve |
|
LGTM label has been added. DetailsGit tree hash: da8a31d8e834a6d54e394de3119ed94bd26ccf89 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xrstf The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Summary
The api-syncagent gets the
LogicalClusterto resolve the logical cluster name and path. However, this is not reflected in theClusterRoledescribed in the "Getting Started" guide. Additionally, if we create theAPIExportfor the api-syncagent in a workspace other than root, we also need to explicitly grant the user access to it.This PR adds the missing RBAC rule to the existing
ClusterRoleand an additionalClusterRoleBindingto grant the access to the workspace.Release Notes