Closed tenaciousdlg closed 2 months ago
Isn't port 3024 used by the proxy service (not auth)?
Edit: I see, it is under the proxy section and auth is the downstream service.
TBH, I'm not even sure how we define downstream service. Auth does not connect to proxy:3024.
The docs show Auth service. What drove this is in the Ports without TLS routing section we did not see anything for App Access. There does not appear to be specific call outs for Database or Kubernetes Access either but I am inferring that Kubernetes goes through SSH?
Sorry Chris, I'm not understanding what you're asking for here.
It should be updated to indicate the protocol type (believe it is SSH) and that this port is used for all reverse tunnel connections
Doesn't it already say this? SSH port used to create reverse SSH tunnels mentions both the protocol (SSH) and that it is used to create reverse tunnels. What am I missing?
The issue we were seeing is that the context reads as it only applies to SSH reverse tunnels whereas it is used for any reverse tunnels (Application Access as an example).
I see. All reverse tunnels in Teleport are SSH reverse tunnels. Seems like that's the confusion and you thought that only applied to server access.
Applies To
https://goteleport.com/docs/reference/networking/
Details
For the following line Teleport only shows the Auth Service as an applicable Downstream service.
It should be updated to indicate the protocol type (believe it is SSH) and that this port is used for all reverse tunnel connections (something like App Access would use this too).
How will we know this is resolved?
When the doc is updated to the scope that it includes the additional information.
Related Issues