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.

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 Policy and Graph Explorer verbiage in teleport-policy guide #50412

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mmcallister
Copy link
Contributor

For update request via #50411.
Changes made in the admin-guides/teleport-policy pages; I'll go through the rest of the doc and update as well if these edits look ok.

cc @roraback

Copy link

🤖 Vercel preview here: https://docs-i54z7vtx4-goteleport.vercel.app/docs

---

Access Graph's Crown Jewel feature allows you to track changes to access for
Graph Explorer's Crown Jewel feature allows you to track changes to access for
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been splitting this out into another feature, and calling it Teleport Policy Crown Jewels

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @benarent! I'll update this and the other references when I get back from vacation, 12/30.

- For self-hosted clusters, a running Access Graph node v1.24.0 or later.
Check [Access Graph page](teleport-policy.mdx) for details on
how to set up Access Graph.
- For self-hosted clusters, a running Graph Explorer node v1.24.0 or later.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically we run access graph service for Teleport Policy https://gallery.ecr.aws/gravitational/access-graph

@@ -95,16 +94,16 @@ it's possible to reuse it as long as the following requirements are met:

- On step 2, you match the `discovery_group` with the existing Discovery Service's
`discovery_group`.
- Access Graph service is reachable from the machine where Discovery Service runs.
- Graph Explorer service is reachable from the machine where Discovery Service runs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of this is good, but I would note again that we run the access graph service for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

docs: update Policy and Graph Explorer verbiage
2 participants