updating new logo diagrams from design team

gravitational · Jan 7, 2025 · 411b1cd · 411b1cd
1 parent eb5a4d1
commit 411b1cd
Show file tree

Hide file tree

Showing 31 changed files with 8 additions and 13 deletions.
diff --git a/docs/img/architecture/agent-architecture.png b/docs/img/architecture/agent-architecture.png
diff --git a/docs/img/architecture/certs-machine-id.png b/docs/img/architecture/certs-machine-id.png
diff --git a/docs/img/architecture/certs-machine-id@1.8x.svg b/docs/img/architecture/certs-machine-id@1.8x.svg
diff --git a/docs/img/architecture/k8s-tunnel.png b/docs/img/architecture/k8s-tunnel.png
diff --git a/docs/img/architecture/proxy-peering.png b/docs/img/architecture/proxy-peering.png
diff --git a/docs/img/architecture/proxy-peering@1.2x.png b/docs/img/architecture/proxy-peering@1.2x.png
diff --git a/docs/img/architecture/proxy-tunnel.png b/docs/img/architecture/proxy-tunnel.png
diff --git a/docs/img/architecture/proxy-tunnel@1.2x.png b/docs/img/architecture/proxy-tunnel@1.2x.png
diff --git a/docs/img/architecture/ssh-direct-mode.png b/docs/img/architecture/ssh-direct-mode.png
diff --git a/docs/img/architecture/ssh-direct-mode@1.2x.png b/docs/img/architecture/ssh-direct-mode@1.2x.png
diff --git a/docs/img/architecture/ssh-tunnel-mode.png b/docs/img/architecture/ssh-tunnel-mode.png
diff --git a/docs/img/architecture/ssh-tunnel-mode@1.2x.png b/docs/img/architecture/ssh-tunnel-mode@1.2x.png
diff --git a/docs/img/architecture/ssh-tunnel-mode@1.2x.svg b/docs/img/architecture/ssh-tunnel-mode@1.2x.svg
diff --git a/docs/img/architecture/tls-routing-alb.png b/docs/img/architecture/tls-routing-alb.png
diff --git a/docs/img/architecture/tls-routing-connection-upgrade.png b/docs/img/architecture/tls-routing-connection-upgrade.png
diff --git a/docs/img/architecture/trusted-clusters.png b/docs/img/architecture/trusted-clusters.png
diff --git a/docs/img/architecture/trusted-clusters@1.5x.svg b/docs/img/architecture/trusted-clusters@1.5x.svg
diff --git a/docs/img/database-access/guides/docdb_cloud.png b/docs/img/database-access/guides/docdb_cloud.png
diff --git a/docs/img/database-access/guides/docdb_cloud.svg b/docs/img/database-access/guides/docdb_cloud.svg
diff --git a/docs/img/database-access/guides/docdb_selfhosted.png b/docs/img/database-access/guides/docdb_selfhosted.png
diff --git a/docs/img/database-access/guides/docdb_selfhosted.svg b/docs/img/database-access/guides/docdb_selfhosted.svg
diff --git a/docs/img/k8s/auth.png b/docs/img/k8s/auth.png
diff --git a/docs/img/server-access/getting-started-diagram.png b/docs/img/server-access/getting-started-diagram.png
diff --git a/docs/img/server-access/openssh-proxy.png b/docs/img/server-access/openssh-proxy.png
diff --git a/docs/pages/enroll-resources/database-access/enroll-aws-databases/aws-docdb.mdx b/docs/pages/enroll-resources/database-access/enroll-aws-databases/aws-docdb.mdx
@@ -11,10 +11,10 @@ description: How to access Amazon DocumentDB with Teleport database access
 
 <Tabs>
 <TabItem label="Self-Hosted">
-![Teleport Architecture DocumentDB Access Self-Hosted](../../../../img/database-access/guides/docdb_selfhosted.svg)
+![Teleport Architecture DocumentDB Access Self-Hosted](../../../../img/database-access/guides/docdb_selfhosted.png)
 </TabItem>
 <TabItem label="Cloud-Hosted">
-![Teleport Architecture DocumentDB Cloud](../../../../img/database-access/guides/docdb_cloud.svg)
+![Teleport Architecture DocumentDB Cloud](../../../../img/database-access/guides/docdb_cloud.png)
 </TabItem>
 
 </Tabs>

diff --git a/docs/pages/reference/architecture/agents.mdx b/docs/pages/reference/architecture/agents.mdx
@@ -133,7 +133,7 @@ In direct mode, SSH Service instances act like OpenSSH servers that only accept
 client SSH certificates. Users can connect to SSH servers through the Teleport
 Proxy Service as a jump-host or directly:
 
-![Standard Mode](../../../img/architecture/ssh-direct-mode@1.2x.png)
+![Standard Mode](../../../img/architecture/ssh-direct-mode.png)
 
 Direct mode is designed for legacy use cases and only supports self-hosted
 Teleport clusters. We recommend joining agents through the Teleport Proxy

diff --git a/docs/pages/reference/architecture/authentication.mdx b/docs/pages/reference/architecture/authentication.mdx
@@ -136,7 +136,7 @@ services and rotates SSH and X.509 certificates.
   caption="Machine-ID certs"
   >
 
-![Certificates for services](../../../img/architecture/certs-machine-id@1.8x.svg)
+![Certificates for services](../../../img/architecture/certs-machine-id.png)
 </Figure>
 
 ### Internal certificates

diff --git a/docs/pages/reference/architecture/authorization.mdx b/docs/pages/reference/architecture/authorization.mdx
@@ -74,7 +74,7 @@ of non-interactive users:
   caption="Machine-ID certs"
   >
 
-![Certificates for services](../../../img/architecture/certs-machine-id@1.8x.svg)
+![Certificates for services](../../../img/architecture/certs-machine-id.png)
 </Figure>
 
 #### External non-interactive users

diff --git a/docs/pages/reference/architecture/proxy-peering.mdx b/docs/pages/reference/architecture/proxy-peering.mdx
@@ -44,7 +44,7 @@ By default, in Proxy Peering mode, agents are configured to connect to a single
 Teleport Proxy instance. For high availability a cluster administrator may
 configure agents to connect to 2 or more Teleport Proxy instances.
 
-![Teleport Proxy Peering](../../../img/architecture/proxy-peering@1.2x.png)
+![Teleport Proxy Peering](../../../img/architecture/proxy-peering.png)
 
 ## Next Steps
 - See the [migration guide](../../admin-guides/management/operations/proxy-peering.mdx) to learn how to upgrade an existing cluster to use

diff --git a/docs/pages/reference/architecture/proxy.mdx b/docs/pages/reference/architecture/proxy.mdx
@@ -63,7 +63,7 @@ Proxies will forward client's connections to target resources via those tunnels.
 
 In the example below, Alice connects to kubernetes cluster behind firewall via two tunnels:
 
-![Teleport Proxy Tunnel](../../../img/architecture/proxy-tunnel@1.2x.png)
+![Teleport Proxy Tunnel](../../../img/architecture/proxy-tunnel.png)
 
 <Notice type="tip">
 All modes above are turned on by default in Proxies. No special configuration is necessary, unless you

diff --git a/docs/pages/reference/architecture/trustedclusters.mdx b/docs/pages/reference/architecture/trustedclusters.mdx
@@ -33,7 +33,7 @@ for your organization. It can have it's own independent resources connected to i
 logs collection and single-sign-on.
 - Clusters `us-east-1a` and `us-east-1b` are two independent clusters in different availability zones.
 
-![Trusted clusters](../../../img/architecture/trusted-clusters@1.5x.svg)
+![Trusted clusters](../../../img/architecture/trusted-clusters.png)
 
 ## Role Mapping