📖 docs: add missing RBAC bindings / rules #50
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The api-syncagent gets the
LogicalCluster
to resolve the logical cluster name and path. However, this is not reflected in theClusterRole
described in the "Getting Started" guide. Additionally, if we create theAPIExport
for 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
ClusterRole
and an additionalClusterRoleBinding
to grant the access to the workspace.Release Notes