-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Fix Machine ID selection of Kubernetes Access address/port #34202
Conversation
Backport will exclude the docs changes (b23d53a) and a separate PR will be raised when this change is released to include a note specifying the version this is fixed within. |
🤖 Vercel preview here: https://docs-2bzf99jy2-goteleport.vercel.app/docs/ver/preview |
🤖 Vercel preview here: https://docs-owf6bnt78-goteleport.vercel.app/docs/ver/preview |
🤖 Vercel preview here: https://docs-o3nc1dalo-goteleport.vercel.app/docs/ver/preview |
🤖 Vercel preview here: https://docs-i5nvhxbnr-goteleport.vercel.app/docs/ver/preview |
🤖 Vercel preview here: https://docs-76tjusnok-goteleport.vercel.app/docs/ver/preview |
🤖 Vercel preview here: https://docs-5bwebroa4-goteleport.vercel.app/docs/ver/preview |
🤖 Vercel preview here: https://docs-4euiyivz1-goteleport.vercel.app/docs/ver/preview |
@strideynet See the table below for backport results.
|
* Improve selection of Kubernetes port and SNI * Add additional test just for connection selektion * Remove docs related to this bug * Open Kube listener in kube test * Use `client.GetKubeTLSServerName` * Remove extranoues space
Closes #19811 / Semi-closes #34178
Addresses a few long standing issues w/ the selection of what address to use when tbot generates the
kubeconfig
file. This also feels a bit neater/more explicit than the previous code and I've also included more tests to cover this process since there's a few edgecases.changelog: Fixes issue where
tbot
would select the wrong address for Kubernetes Access when in ports separate mode.