Skip to content

docs: Convert text links to TileGrid for MWI configuration and deployment #59775

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

Merged
merged 4 commits into from
Oct 16, 2025
Merged

docs: Convert text links to TileGrid for MWI configuration and deployment #59775

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
07e864e
docs: drafting tiled approach for mwi
mmcallister Sep 30, 2025
5ff927a
editing tilegrid icons and paths
mmcallister Oct 3, 2025
5e2f7f9
adding cicd tilegrid to deployment page
mmcallister Oct 9, 2025
6d6b776
icon and path changes
mmcallister Oct 14, 2025
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
151 changes: 117 additions & 34 deletions docs/pages/machine-workload-identity/machine-id/deployment/deployment.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,46 +42,129 @@ authentication methods:

## Deployment guides

The guides in this section show you how to deploy Machine ID and join it
to your cluster. Choose a guide based on the platform where you intend to run
Machine ID.
The guides in this section show you how to deploy Machine ID and join it to your cluster.
Choose a guide based on the platform where you intend to run Machine ID.

If a specific guide does not exist for your platform, the [Linux
guide](linux.mdx) is compatible with most platforms. For
custom approaches, you can also read the [Machine ID Reference](../../../reference/machine-workload-identity/machine-id/machine-id.mdx)
and [Architecture](../../../reference/architecture/machine-id-architecture.mdx) to plan your deployment.

### Self-hosted infrastructure

Read the following guides for how to deploy Machine ID on your cloud platform or
on-prem infrastructure.

| Platform | Installation method | Join method |
|----------------------------------------|-------------------------------------------------|-----------------------------------------------------|
| [Linux](linux.mdx) | Package manager or TAR archive | Static join token |
| [Linux (TPM)](linux-tpm.mdx) | Package manager or TAR archive | Attestation from TPM 2.0 |
| [Linux (Bound Keypair)][bound-keypair] | Package manager or TAR archive | Bound Keypair |
| [GCP](gcp.mdx) | Package manager, TAR archive, or Kubernetes pod | Identity document signed by GCP |
| [AWS](aws.mdx) | Package manager, TAR archive, or Kubernetes pod | Identity document signed by AWS |
| [Azure](azure.mdx) | Package manager or TAR archive | Identity document signed by Azure |
| [Kubernetes](kubernetes.mdx) | Kubernetes pod | Identity document signed by your Kubernetes cluster |
| [Kubernetes OIDC](kubernetes-oidc.mdx) | Kubernetes pod on a cloud provider with OIDC | Identity document signed by your cloud provider |
<TileGrid
tiles={[
{
icon: <Icon name="aws" size="xl" />,
to: "./aws",
name: "AWS",
},
{
icon: <Icon name="azure" size="xl" />,
to: "./azure",
name: "Azure",
},
{
icon: <Icon name="azureDevops" size="xl" />,
to: "./azure-devops",
name: "Azure DevOps",
},
{
icon: <Icon name="bitbucket" size="xl" />,
to: "./bitbucket",
name: "BitBucket Pipelines",
},
{
icon: <Icon name="circleci" size="xl" />,
to: "./circleci",
name: "CircleCI",
},
{
icon: <Icon name="gitlab" size="xl" />,
to: "./gitlab",
name: "GitLab CI",
},
{
icon: <Icon name="githubActions" size="xl" />,
to: "./github-actions",
name: "GitHub Actions",
},
{
icon: <Icon name="googleCloud" size="xl" />,
to: "./gcp",
name: "Google Cloud",
},
{
icon: <Icon name="kubernetes2" size="xl" />,
to: "./kubernetes",
name: "Kubernetes",
},
{
icon: <Icon name="kubernetes" size="xl" />,
to: "./kubernetes-oidc",
name: "Kubernetes OIDC",
},
{
icon: <Icon name="linux" size="xl" />,
to: "./linux",
name: "Linux",
},
{
icon: <Icon name="linux-servers" size="xl" />,
to: "./linux-tpm",
name: "Linux TPM",
},
{
icon: <Icon name="lock" size="xl" />,
to: "../../reference/machine-workload-identity/machine-id/bound-keypair/getting-started",
Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, looks like this link is broken? I think it needs one more ../?

name: "Bound Keypair Joining",
}
]}
/>

### CI/CD

Read the following guides for how to deploy Machine ID on a continuous
integration and continuous deployment platform

| Platform | Installation method | Join method |
|--------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|------------------------------------------|
| [Azure DevOps](azure-devops.mdx) | TAR archive | Azure DevOps-signed identity document |
| [Bitbucket Pipelines](bitbucket.mdx) | TAR archive | Bitbucket-signed identity document |
| [CircleCI](circleci.mdx) | TAR archive | CircleCI-signed identity document |
| [GitLab](gitlab.mdx) | TAR archive | GitLab-signed identity document |
| [GitHub Actions](github-actions.mdx) | Teleport job available through the GitHub Actions marketplace | GitHub-signed identity document. |
| [Jenkins](jenkins.mdx) | Package manager or TAR archive | Static join token |
| [Spacelift](../../../zero-trust-access/infrastructure-as-code/terraform-provider/spacelift.mdx) | Docker Image | Spacelift-signed identity document |
| [Terraform Cloud](../../../zero-trust-access/infrastructure-as-code/terraform-provider/terraform-cloud.mdx) | Teleport Terraform Provider via Teleport's Terraform Registry | Terraform Cloud-signed identity document |


[bound-keypair]: ../../../reference/machine-workload-identity/machine-id/bound-keypair/getting-started.mdx
Read the following guides for how to deploy Machine ID on a continuous integration and continuous deployment platform.

<TileGrid
tiles={[
{
icon: <Icon name="azureDevops" size="xl" />,
to: "./azure-devops",
name: "Azure DevOps",
},
{
icon: <Icon name="bitbucket" size="xl" />,
to: "./bitbucket",
name: "BitBucket Pipelines",
},
{
icon: <Icon name="circleci" size="xl" />,
to: "./circleci",
name: "CircleCI",
},
{
icon: <Icon name="gitlab" size="xl" />,
to: "./gitlab",
name: "GitLab CI",
},
{
icon: <Icon name="githubActions" size="xl" />,
to: "./github-actions",
name: "GitHub Actions",
},
{
icon: <Icon name="jenkins" size="xl" />,
to: "./jenkins",
name: "Jenkins",
},
{
icon: <Icon name="spacelift" size="xl" />,
to: "../../zero-trust-access/infrastructure-as-code/terraform-provider/spacelift",
name: "Spacelift",
},
{
icon: <Icon name="terraform" size="xl" />,
to: "../../zero-trust-access/infrastructure-as-code/terraform-provider/terraform-cloud",
name: "Terraform Cloud",
}
]}
/>
40 changes: 33 additions & 7 deletions docs/pages/machine-workload-identity/workload-identity/workload-identity.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,14 +14,40 @@ issues flexible short-lived identities to workloads in your infrastructure.
- [Introduction to SPIFFE](./spiffe.mdx): Learn about Secure Production Identity Framework For Everyone (SPIFFE) and how it is implemented by Teleport Workload Identity
- [Getting Started with Workload Identity](./getting-started.mdx): Getting started with Teleport Workload Identity for SPIFFE and Machine ID

## Guides
- [Configuring Workload Identity and AWS OIDC Federation](./aws-oidc-federation.mdx): Configuring AWS to accept Workload Identity JWTs as authentication using OIDC Federation
- [Configuring Workload Identity and AWS Roles Anywhere](./aws-roles-anywhere.mdx): Configuring AWS to accept Workload Identity certificates as authentication using AWS Roles Anywhere
- [Configuring Workload Identity and Azure Federated Credentials](./azure-federated-credentials.mdx): Configuring Azure to accept Workload Identity JWTs as authentication using Azure Federated Credentials
- [Configuring Workload Identity and GCP Workload Identity Federation with JWTs](./gcp-workload-identity-federation-jwt.mdx): Configuring GCP to accept Workload Identity JWTs as authentication using Workload Identity Federation
- [Workload Identity and tsh](./tsh.mdx): Issuing SPIFFE SVIDs using Workload Identity and tsh
## Configuration Guides

## Configuration & management
<TileGrid
tiles={[
{
icon: <Icon name="aws" size="xl" />,
to: "./aws-oidc-federation",
name: "AWS OIDC Federation",
},
{
icon: <Icon name="awsIdentity" size="xl" />,
to: "./aws-roles-anywhere",
name: "AWS Roles Anywhere",
},
{
icon: <Icon name="azure" size="xl" />,
to: "./azure-federated-credentials",
name: "Azure Federated Credentials",
},
{
icon: <Icon name="googleCloud" size="xl" />,
to: "./gcp-workload-identity-federation-jwt",
name: "GCP Workload Identity Federation",
},
{
icon: <Icon name="code" size="xl" />,
to: "./tsh",
name: "Manually issue SPIFFE SVIDs with Teleport CLI tool tsh",
}
]}
/>


## Configuration management
- [Best Practices for Teleport Workload Identity](./best-practices.mdx): Answers common questions and describes best practices for using Teleport Workload Identity in production.
- [JWT SVIDs](./jwt-svids.mdx): An overview of the JWT SVIDs issued by Teleport Workload Identity
- [SPIFFE Federation](./federation.mdx): An overview of the Teleport Workload Identity SPIFFE Federation feature.
Expand Down
Loading