Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update role mapping instrs for trusted clusters #48285

Closed
wants to merge 1 commit into from
Closed

docs: update role mapping instrs for trusted clusters #48285

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions docs/pages/admin-guides/management/admin/trustedclusters.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -700,13 +700,17 @@ Reference](../../../reference/access-controls/roles.mdx).

### Update role mappings

You can update role mappings for a trusted cluster resource by modifying the `role_map`
field in the `trusted_cluster.yaml` resource configuration file. After you update the
resource configuration file, you can update the trusted cluster by signing in to the
leaf cluster and running the following command:
Modifications to the role mappings for a trusted cluster resource
require deleting and re-creating the trust relationship. See
[remove a trusted leaf cluster](#remove-a-trusted-leaf-cluster) to remove the trust relationship.

After removing you can update the `role_map` within the `trusted_cluster.yaml`
resource configuration file on the leaf cluster. Confirm the token value is still
valid which may have expired. Run this command to re-create the trust relationship
with the new role mapping:

```code
$ tctl create --force trusted_cluster.yaml
$ tctl create trusted_cluster.yaml
```

### Role mapping and cluster-level labels
Expand Down
Loading