-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update aws-gslb-proxy-peering-ha-deployment.mdx #48916
base: master
Are you sure you want to change the base?
Conversation
Several customers have been confused by the restrictive language stating that an NLB is required. This was true when the guide was first written but is no longer the case. I've added language that indicates that using an AWS ALB is an option.
docs/pages/admin-guides/deploy-a-cluster/deployments/aws-gslb-proxy-peering-ha-deployment.mdx
Outdated
Show resolved
Hide resolved
This pull request is automatically being deployed by Amplify Hosting (learn more). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, assuming Zac's feedback is addressed
🤖 Vercel preview here: https://docs-4c5sk5bjd-goteleport.vercel.app/docs/ver/preview |
…proxy-peering-ha-deployment.mdx Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
@zmb3 I believe the use of ALB with multiplexing was enabled as far back as v13 so should this be backported all the way back to that version? |
🤖 Vercel preview here: https://docs-5h8nu64m0-goteleport.vercel.app/docs/ver/preview |
No, the v13 docs aren't published to goteleport.com anymore (and the v14 docs will be removed very soon) |
🤖 Vercel preview here: https://docs-9mduc5a50-goteleport.vercel.app/docs/ver/preview |
🤖 Vercel preview here: https://docs-cv0ox4bf7-goteleport.vercel.app/docs/ver/preview |
Amplify deployment status
|
Do we want users to prefer NLBs when possible? Going through ALBs is done via the upgrade-to-mTLS-in-websocket and adds an encapsulation level, causing the handshakes to be slower and more expensive. This matters in bad connectivity/high latency scenarios (e.g. connecting to a cluster located in a distant region). |
@hugoShaka NLB is implicitly the preference by using it for the example. The issue I'm trying to solve is there have been several customers opening support cases or spending time trying to figure out how to satisfy the NLB requirement even though ALB is now an option for this setup. |
Several customers have been confused by the restrictive language stating that an NLB is required. This was true when the guide was first written but is no longer the case. I've added language that indicates that using an AWS ALB is an option.