docs: update cloud networking on proxy service (#47506)

* docs: update cloud networking on proxy service * docs: update verbiage for networking Co-authored-by: Paul Gottschling <[email protected]> * docs: update cloud-hosted public address * docs: update verbiage for app access for networking * docs: update verbiage for public address for networks with cloud Co-authored-by: Paul Gottschling <[email protected]> * docs: clarify app configuration * docs: update cloud-hosted explanation for public address --------- Co-authored-by: Paul Gottschling <[email protected]>
gravitational · Oct 30, 2024 · 043411c · 043411c
1 parent 6dc63a0
commit 043411c
Showing 1 changed file with 2 additions and 14 deletions.
diff --git a/docs/pages/reference/networking.mdx b/docs/pages/reference/networking.mdx
@@ -36,21 +36,9 @@ following use cases:
 </TabItem>
 <TabItem scope={["cloud", "team"]} label="Cloud-Hosted">
 
-All Teleport services (e.g., the Application Service and Database Service) have
-an optional `public_addr` property that you can modify in each service's
-configuration file. The public address can take an IP or a DNS name. It can also
-be a list of values:
-
-```yaml
-public_addr: ["service-one.example.com", "service-two.example.com"]
-```
+On Teleport Enterprise (Cloud) the Teleport agent services always
+connect using reverse tunnels so there is no need to set a public address for a agent.
 
-Specifying a public address for a Teleport agent may be useful in the
-following use cases:
-
-- You have multiple identical services behind a load balancer.
-- You want Teleport to issue an SSH certificate for the service with additional
-  principals, e.g., host names.
 </TabItem>
 </Tabs>