docs: update cloud networking on proxy service #47506
Conversation
stevenGravy
added
backport/branch/v14
no-changelog
github-actions
bot
requested review from
mmcallister,
ptgott,
r0mant,
xinding33 and
zmb3
|
🤖 Vercel preview here: https://docs-8xw7dmj3b-goteleport.vercel.app/docs/ver/preview |
docs/pages/reference/networking.mdx
Outdated
| For Teleport Enterprise Cloud all Teleport services (e.g. Kubernetes Service, | ||
| SSH Service,...) connect via reverse tunnels through the Teleport Proxy Service. | ||
| The Teleport Proxy Service and Auth Service are provided so no specification | ||
| is required for those. This makes the usage of `public_addr` limited to the Application Service. |
There was a problem hiding this comment.
It looks like we are introducing the public_addr property in this Tabs component, so a user won't understand what "the usage of public_addr" means.
I think we can structure the content of this TabItem to mention the public_addr property for Teleport Enterprise (Cloud) users as though it is only available for the Application Service, indicating why a user would want to set this property.
There was a problem hiding this comment.
thanks @ptgott , please see update
Co-authored-by: Paul Gottschling <[email protected]>
|
🤖 Vercel preview here: https://docs-cerbfamm8-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-bqckpeuiw-goteleport.vercel.app/docs/ver/preview |
This presented as if you could expose public addresses for Teleport services with in Ent Cloud. Since you can only do reverse tunnel that isn't accurate.