GCP LB timeout recommendation #52312
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When customers use the default GCP LB timeout value of 30 seconds, agents disconnect due to the Teleport keepalive_interval being higher by default.
WilliamLoy
temporarily deployed
to
docs-amplify
GitHub Actions
Inactive
github-actions
bot
added
documentation
no-changelog
github-actions
bot
requested review from
hugoShaka,
mmcallister,
ptgott,
r0mant,
xinding33 and
zmb3
|
Amplify deployment status
|
ptgott
approved these changes
Feb 19, 2025
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
hugoShaka
reviewed
Mar 12, 2025
| @@ -117,6 +117,10 @@ storage: | |||
| Load Balancing is required for Proxy and SSH traffic. Use `TCP Load Balancing` as | |||
| Teleport requires custom ports for SSH and Web Traffic. | |||
|
|
|||
| GCP sets a default Load Balancer timeout of 30 seconds. You should either increase this to be longer than the Teleport Auth Service default keepalive interval of 300 seconds or decrease the Teleport `keep_alive_interval` to be lower than the GCP timeout value. | |||
There was a problem hiding this comment.
This information is incomplete and not true in most cases.
AFAIK GCP does not have a concept of timeout for Passthrough TCP/UDP LBs, not for Proxy TCP/UDP LBs. The 30 second timeout is only on Application LBs (L7/HTTP) and varies based on the target type (target pool vs NEG).
The guide instructs users to use L4 LBs so they should not have to set the timeout (and I don't even think it's possible to set the L4 Lb timeout in GCP).
There was a problem hiding this comment.
I made revisions that I believe avoid inaccurate information while still informing the reader that L7 is an available option.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When customers use the default GCP LB timeout value of 30 seconds, agents disconnect due to the Teleport keepalive_interval being higher by default.