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

Workload ID: Restructure docs to be more value-first #47637

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

strideynet
Copy link
Contributor

Since we don't have a general landing page for Workload ID on the main marketing site, I figured it made some sense to try and make the Workload Identity introduction on the docs focus a little more on the potential use-cases and value - rather than diving straight into the technical deep-end.

Copy link

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

Copy link

🤖 Vercel preview here: https://docs-5gce73z6h-goteleport.vercel.app/docs/ver/preview

Copy link

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

Copy link

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

Comment on lines +28 to +38
There's a whole host of benefits to adopting Teleport Workload Identity, but
here's some of the key ones:

- Eliminate the use of long-lived shared secrets within your infrastructure, and
reduce the risk of exfiltration and time spent by engineers creating and
rotating these secrets.
- Establish an out of the box universal form of identity for your workloads,
enabling your engineers to get on with building new services without needing
to think about how they'll authenticate.
- Converge on a first-class form of identity for your workloads, simplifying
infrastructure by reducing the number of different ways workloads authenticate.
Copy link
Contributor

@ptgott ptgott Oct 17, 2024

Choose a reason for hiding this comment

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

I would shorten this introductory section by combining the list of benefits with the list of use cases (and choosing three bullets total). That way, we can move past the generalities more quickly and get to the substantive details about how Workload Identity works and what it means in Teleport.

SPIFFE sets out:

- A format for uniquely specifying an identity, the SPIFFE ID.
- Standards for encoding the SPIFFE ID into verifiable documents, the SVID.
Copy link
Contributor

Choose a reason for hiding this comment

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

What does "the SVID" modify here? Is it a rephrasing of "standards"?

- Processes that workloads should use to validate a received SVID.
- A set of APIs that workloads can use to request SVIDS, the Workload API.

The open nature and popularity of SPIFFE make it a great choice as a foundation
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a way to use a more objective-sounding word than "great" here?

docs/pages/enroll-resources/workload-identity/spiffe.mdx Outdated Show resolved Hide resolved
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
@strideynet strideynet added the no-changelog Indicates that a PR does not require a changelog entry label Oct 17, 2024
Copy link

🤖 Vercel preview here: https://docs-1zflfb9ky-goteleport.vercel.app/docs/ver/preview

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

Successfully merging this pull request may close these issues.

2 participants