Skip to content

Commit 1c9c648

Browse files
ptgottptgott
committed
Remove Figure tags
See gravitational/docs-website#95 The docs engine currently unwraps them, meaning that they are no-op components. Remove these so we can delete the Figure-unwrapping code.
1 parent 0603d5f commit 1c9c648

File tree

26 files changed

+53
-254
lines changed

26 files changed

+53
-254
lines changed

‎docs/pages/admin-guides/access-controls/guides/headless.mdx

-4
Original file line numberDiff line numberDiff line change
@@ -181,15 +181,11 @@ Teleport Connect v13.3.1+ can also be used to approve Headless WebAuthn logins.
181181
Teleport Connect will automatically detect the Headless WebAuthn login attempt
182182
and allow you to approve or cancel the request.
183183

184-
<Figure width="700">
185184
![Headless Confirmation](../../../../img/headless/confirmation.png)
186-
</Figure>
187185

188186
You will be prompted to tap your MFA key to complete the approval process.
189187

190-
<Figure width="700">
191188
![Headless WebAuthn Approval](../../../../img/headless/approval.png)
192-
</Figure>
193189

194190
<Admonition type="note">
195191
This also requires a v13.3.1+ Teleport Auth Service.

‎docs/pages/admin-guides/deploy-a-cluster/helm-deployments/digitalocean.mdx

+14-21
Original file line numberDiff line numberDiff line change
@@ -21,15 +21,13 @@ cluster to Teleport.
2121
## Step 1/4. Create a DigitalOcean Kubernetes cluster
2222

2323
Create a new [DigitalOcean Kubernetes Cluster](https://cloud.digitalocean.com/kubernetes/clusters/)
24-
<Figure align="left" bordered caption="Create DigitalOcean Kubernetes cluster">
25-
![Create DigitalOcean Kubernetes cluster](../../../../img/helm/digitalocean/create-k8s.png)
26-
</Figure>
24+
25+
![Create DigitalOcean Kubernetes cluster](../../../../img/helm/digitalocean/create-k8s.png)
2726

2827
<br />
2928
While the Kubernetes cluster is being provisioned, follow the "Getting Started" guide as shown below:
30-
<Figure align="left" bordered caption="Set up DigitalOcean Kubernetes client">
31-
![Set up DigitalOcean Kubernetes client](../../../../img/helm/digitalocean/setup-k8s.png)
32-
</Figure>
29+
30+
![Set up DigitalOcean Kubernetes client](../../../../img/helm/digitalocean/setup-k8s.png)
3331

3432
## Step 2/4. Install Teleport
3533

@@ -116,9 +114,8 @@ teleport-cluster-auth ClusterIP 10.245.164.28 <none> 3025/TC
116114
```
117115

118116
Once you get the value for the external IP (it may take a few minutes for this field to be populated), update your DNS record such that the clusterName's A record points to this IP address. For example `192.168.200.200` is the external IP in the above case.
119-
<Figure align="left" bordered caption="Configure DNS">
120-
![Configure DNS](../../../../img/helm/digitalocean/fqdn.png)
121-
</Figure>
117+
118+
![Configure DNS](../../../../img/helm/digitalocean/fqdn.png)
122119

123120
## Step 3/4. Create and set up Teleport user
124121
Now we create a Teleport user by executing the `tctl` command with `kubectl`.
@@ -148,9 +145,8 @@ NOTE: Make sure tele.example.com:443 points at a Teleport proxy which users can
148145
</Tabs>
149146

150147
Copy the link shown after executing the above command and open the link in a web browser to complete the user registration process (the link is `https://tele.example.com:443/web/invite/<invite-token>` in the above case).
151-
<Figure align="left" bordered caption="Set up user">
152-
![Set up user](../../../../img/helm/digitalocean/setup-user.png)
153-
</Figure>
148+
149+
![Set up user](../../../../img/helm/digitalocean/setup-user.png)
154150

155151
After you complete the registration process by setting up a password and enrolling in multi-factor authentication, you will be logged in to Teleport Web UI.
156152

@@ -179,14 +175,12 @@ $ kubectl --namespace=teleport-cluster exec -i deployment/teleport-cluster-auth
179175

180176
Now we will assign Teleport user **tadmin** with this role. The example below shows a process using Teleport Web UI:
181177
First, lets select user edit menu:
182-
<Figure align="left" bordered caption="Edit user">
183-
![Edit user](../../../../img/helm/digitalocean/edit-user.png)
184-
</Figure>
178+
179+
![Edit user](../../../../img/helm/digitalocean/edit-user.png)
185180

186181
Second, update the **tadmin** user role to assign the **member** role:
187-
<Figure align="left" bordered caption="Update role">
188-
![Update role](../../../../img/helm/digitalocean/update-role.png)
189-
</Figure>
182+
183+
![Update role](../../../../img/helm/digitalocean/update-role.png)
190184

191185
We've updated the user **tadmin** to have the **member** role, which is allowed to access a Kubernetes cluster with privilege `system:master`.
192186

@@ -263,9 +257,8 @@ teleport-cluster-6cc679b6f6-7xr5h 1/1 Running 0 14h
263257
Voila! User **tadmin** was able to list the pods in their DigitalOcean Kubernetes cluster.
264258

265259
Teleport keeps an audit log of access to a Kubernetes cluster. In the screenshot below, the Teleport audit log shows that the user **tadmin** has logged into the cluster.
266-
<Figure align="left" bordered caption="View audit log">
267-
![View audit log](../../../../img/helm/digitalocean/view-activity.png)
268-
</Figure>
260+
261+
![View audit log](../../../../img/helm/digitalocean/view-activity.png)
269262

270263
## Next steps
271264

‎docs/pages/admin-guides/deploy-a-cluster/helm-deployments/gcp.mdx

+31-62
Original file line numberDiff line numberDiff line change
@@ -39,81 +39,62 @@ Go to the "Roles" section of Google Cloud IAM & Admin.
3939

4040
1. Click the "Create Role" button at the top.
4141

42-
<Figure align="left" bordered caption="Roles section">
43-
![Roles section](../../../../img/helm/gcp/1-roles@1.5x.png)
44-
</Figure>
42+
![Roles section](../../../../img/helm/gcp/1-roles@1.5x.png)
4543

4644
2. Fill in the details of a "Storage Bucket Creator" role (we suggest using the name `storage-bucket-creator-role`)
4745

48-
<Figure align="left" bordered caption="Create role">
49-
![Create role](../../../../img/helm/gcp/2-createrole@1.5x.png)
50-
</Figure>
46+
![Create role](../../../../img/helm/gcp/2-createrole@1.5x.png)
5147

5248
3. Click the "Add Permissions" button.
5349

54-
<Figure align="left" bordered caption="Storage bucket creator role">
55-
![Storage bucket creator role](../../../../img/helm/gcp/3-addpermissions@1.5x.png)
56-
</Figure>
50+
![Storage bucket creator role](../../../../img/helm/gcp/3-addpermissions@1.5x.png)
5751

5852
4. Use the "Filter" box to enter `storage.buckets.create` and select it in the list.
5953

60-
<Figure align="left" bordered caption="Filter the list">
61-
![Filter the list](../../../../img/helm/gcp/4-storagebucketscreate@1.5x.png)
62-
</Figure>
54+
![Filter the list](../../../../img/helm/gcp/4-storagebucketscreate@1.5x.png)
6355

6456
5. Check the `storage.buckets.create` permission in the list and click the "Add" button to add it to the role.
6557

66-
<Figure align="left" bordered caption="Select storage.buckets.create">
67-
![Select storage.buckets.create](../../../../img/helm/gcp/5-select@1.5x.png)
68-
</Figure>
58+
![Select storage.buckets.create](../../../../img/helm/gcp/5-select@1.5x.png)
6959

7060
6. Once all these settings are entered successfully, click the "Create" button.
7161

72-
<Figure align="left" bordered caption="Create role">
73-
![Create role](../../../../img/helm/gcp/6-createrole@1.5x.png)
74-
</Figure>
62+
![Create role](../../../../img/helm/gcp/6-createrole@1.5x.png)
7563

7664
### Create an IAM role granting Cloud DNS permissions
7765

7866
Go to the "Roles" section of Google Cloud IAM & Admin.
7967

8068
1. Click the "Create Role" button at the top.
8169

82-
<Figure align="left" bordered caption="Roles section">
83-
![Roles section](../../../../img/helm/gcp/1-roles@1.5x.png)
84-
</Figure>
70+
![Roles section](../../../../img/helm/gcp/1-roles@1.5x.png)
8571

8672
2. Fill in the details of a "DNS Updater" role (we suggest using the name `dns-updater-role`)
8773

88-
<Figure align="left" bordered caption="Create role">
89-
![Create role](../../../../img/helm/gcp/13-dns-createrole@1.5x.png)
90-
</Figure>
74+
![Create role](../../../../img/helm/gcp/13-dns-createrole@1.5x.png)
9175

9276
3. Click the "Add Permissions" button.
9377

94-
<Figure align="left" bordered caption="DNS updater role">
95-
![DNS updater role](../../../../img/helm/gcp/3-addpermissions@1.5x.png)
96-
</Figure>
97-
98-
4. Use the "Filter" box to find each of the following permissions in the list and add it.
99-
You can type things like `dns.resourceRecordSets.*` to quickly filter the list.
100-
101-
```console
102-
dns.resourceRecordSets.create
103-
dns.resourceRecordSets.delete
104-
dns.resourceRecordSets.list
105-
dns.resourceRecordSets.update
106-
dns.changes.create
107-
dns.changes.get
108-
dns.changes.list
109-
dns.managedZones.list
110-
```
78+
![DNS updater role](../../../../img/helm/gcp/3-addpermissions@1.5x.png)
79+
80+
4. Use the "Filter" box to find each of the following permissions in the list
81+
and add it. You can type things like `dns.resourceRecordSets.*` to quickly
82+
filter the list.
83+
84+
```console
85+
dns.resourceRecordSets.create
86+
dns.resourceRecordSets.delete
87+
dns.resourceRecordSets.list
88+
dns.resourceRecordSets.update
89+
dns.changes.create
90+
dns.changes.get
91+
dns.changes.list
92+
dns.managedZones.list
93+
```
11194

11295
5. Once all these settings are entered successfully, click the "Create" button.
11396

114-
<Figure align="left" bordered caption="Add DNS permissions">
115-
![Add DNS permissions](../../../../img/helm/gcp/14-dns-permissions-create@1.5x.png)
116-
</Figure>
97+
![Add DNS permissions](../../../../img/helm/gcp/14-dns-permissions-create@1.5x.png)
11798

11899
### Create a service account for the Teleport Helm chart
119100

@@ -127,15 +108,11 @@ Go to the "Service Accounts" section of Google Cloud IAM & Admin.
127108

128109
1. Click the "Create Service Account" button at the top.
129110

130-
<Figure align="left" bordered caption="Create service account">
131-
![Create service account](../../../../img/helm/gcp/7-serviceaccounts@1.5x.png)
132-
</Figure>
111+
![Create service account](../../../../img/helm/gcp/7-serviceaccounts@1.5x.png)
133112

134113
2. Enter details for the service account (we recommend using the name `teleport-helm`) and click the "Create" button.
135114

136-
<Figure align="left" bordered caption="Enter service account details">
137-
![Enter service account details](../../../../img/helm/gcp/8-createserviceaccount@1.5x.png)
138-
</Figure>
115+
![Enter service account details](../../../../img/helm/gcp/8-createserviceaccount@1.5x.png)
139116

140117
3. In the "Grant this service account access to project" section, add these four roles:
141118

@@ -146,9 +123,7 @@ Go to the "Service Accounts" section of Google Cloud IAM & Admin.
146123
| Cloud Datastore Owner | Grants permissions to create Cloud Datastore collections |
147124
| Storage Object Admin | Allows read/write/delete of Google Cloud storage objects |
148125

149-
<Figure align="left" bordered caption="Add roles">
150-
![Add roles](../../../../img/helm/gcp/9-addroles@1.5x.png)
151-
</Figure>
126+
![Add roles](../../../../img/helm/gcp/9-addroles@1.5x.png)
152127

153128
4. Click the "continue" button to save these settings, then click the "create" button to create the service account.
154129

@@ -158,22 +133,16 @@ Go back to the "Service Accounts" view in Google Cloud IAM & Admin.
158133

159134
1. Click on the `teleport-helm` service account that you just created.
160135

161-
<Figure align="left" bordered caption="Click on the service account">
162-
![Click on the service account](../../../../img/helm/gcp/10-serviceaccountdetails@1.5x.png)
163-
</Figure>
136+
![Click on the service account](../../../../img/helm/gcp/10-serviceaccountdetails@1.5x.png)
164137

165138
2. Click the "Keys" tab at the top and click "Add Key". Choose "JSON" and click "Create".
166139

167-
<Figure align="left" bordered caption="Create JSON key">
168-
![Create JSON key](../../../../img/helm/gcp/11-createkey.png)
169-
</Figure>
140+
![Create JSON key](../../../../img/helm/gcp/11-createkey.png)
170141

171142
3. The JSON private key will be downloaded to your computer. Take note of the filename (`bens-demos-24150b1a0a7f.json` in this example)
172143
as you will need it shortly.
173144

174-
<Figure align="left" bordered caption="Private key saved">
175-
![Private key saved](../../../../img/helm/gcp/12-privatekey@1.5x.png)
176-
</Figure>
145+
![Private key saved](../../../../img/helm/gcp/12-privatekey@1.5x.png)
177146

178147
#### Create the Kubernetes secret containing the JSON private key for the service account
179148

‎docs/pages/admin-guides/deploy-a-cluster/linux-demo.mdx

-2
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,8 @@ You can also get started right away with a production-ready Teleport cluster by
1515
signing up for a [free trial of Teleport Enterprise
1616
Cloud](https://goteleport.com/signup/).
1717

18-
<Figure width="700">
1918
![Architecture of the setup you will complete in this
2019
guide](../../../img/linux-server-diagram.png)
21-
</Figure>
2220

2321
We will run the following Teleport services:
2422

‎docs/pages/admin-guides/management/export-audit-events/fluentd.mdx

-2
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,7 @@ This guide also serves as an explanation for the Teleport Event Handler plugin,
1414
using Fluentd as the target service. We'll create a local Docker container as a
1515
destination for the Event Handler:
1616

17-
<Figure width="600">
1817
![The Teleport Fluentd plugin](../../../../img/enterprise/plugins/fluentd-diagram.png)
19-
</Figure>
2018

2119
You can follow the instructions below for a local proof-of-concept demo, or use any
2220
of the additional installation instructions to configure the Teleport Event Handler

‎docs/pages/admin-guides/management/guides/ec2-tags.mdx

+2-7
Original file line numberDiff line numberDiff line change
@@ -50,22 +50,17 @@ To launch a new instance with instance metadata tags enabled:
5050
1. Ensure that `Metadata accessible` is not disabled.
5151
1. Enable `Allow tags in metadata`.
5252

53-
<Figure align="left" bordered caption="Advanced Options">
5453
![Advanced Options](../../../../img/aws/launch-instance-advanced-options.png)
55-
</Figure>
5654

5755
To modify an existing instance to enable instance metadata tags:
5856

5957
1. From the instance summary, go to `Actions > Instance Settings > Allow tags in instance metadata`.
60-
1. Enable `Allow`.
6158

62-
<Figure align="left" bordered caption="Instance Settings">
6359
![Instance Settings](../../../../img/aws/instance-settings.png)
64-
</Figure>
6560

66-
<Figure align="left" bordered caption="Allow Tags">
61+
1. Enable `Allow`.
62+
6763
![Allow Tags](../../../../img/aws/allow-tags.png)
68-
</Figure>
6964

7065
### AWS CLI
7166

‎docs/pages/admin-guides/teleport-policy/integrations/entra-id.mdx

-8
Original file line numberDiff line numberDiff line change
@@ -55,24 +55,18 @@ navigate to the "Access Management" tab, and choose "Enroll New Integration", th
5555

5656
In the onboarding wizard, choose a Teleport user that will be assigned as the default owner of Access Lists that are created for your Entra groups, and click "Next".
5757

58-
<Figure width="600">
5958
![First step of the Entra ID integration onboarding](../../../../img/access-graph/entra-id/integration-wizard-step-1.png)
60-
</Figure>
6159

6260
## Step 2/3. Grant permissions in Azure and finish onboarding
6361

6462
The wizard will now provide you with a script that will set up the necessary permissions in Azure.
6563

66-
<Figure width="600">
6764
![Second step of the Entra ID integration onboarding](../../../../img/access-graph/entra-id/integration-wizard-step-2.png)
68-
</Figure>
6965

7066
Open Azure Cloud Shell by navigating to <a href="https://shell.azure.com">shell.azure.com</a>,
7167
or by clicking the Cloud Shell icon in the Azure Portal.
7268

73-
<Figure width="600">
7469
![Location of the Cloud Shell button in the Azure Portal](../../../../img/access-graph/entra-id/azure-cloud-shell-button.png)
75-
</Figure>
7670

7771
Make sure to use the Bash version of Cloud Shell.
7872
Once a Cloud Shell instance opens, paste the generated command.
@@ -86,9 +80,7 @@ it prints out the data required to finish the integration onboarding.
8680

8781
Back in the Teleport Web UI, fill out the required data and click "Finish".
8882

89-
<Figure width="600">
9083
![Second step of the Entra ID integration onboarding with required fields filled in](../../../../img/access-graph/entra-id/integration-wizard-step-2-filled.png)
91-
</Figure>
9284

9385
## Step 3/3. Analyze Entra ID directory in Teleport Access Graph
9486

‎docs/pages/admin-guides/teleport-policy/policy-connections.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -76,4 +76,4 @@ Resource Groups are created from Teleport roles.
7676
Resources are created from Teleport resources like nodes, databases, and Kubernetes clusters.
7777

7878
## Next steps
79-
- Uncover [privileges, permissions, and construct SQL queries](./policy-how-to-use.mdx) in Access Graph.
79+
- Uncover [privileges, permissions, and construct SQL queries](./policy-how-to-use.mdx) in Access Graph.

0 commit comments

Comments
 (0)