Add support for Client ID in Azure VM auto-discovery#32360
Conversation
|
🤖 Vercel preview here: https://docs-943ksq91b-goteleport.vercel.app/docs/ver/14.x |
0464480 to
fda6e69
Compare
|
🤖 Vercel preview here: https://docs-a3qgfzw01-goteleport.vercel.app/docs/ver/14.x |
There was a problem hiding this comment.
Can we not introduce a basically free-form arbitrary "join params" field that's easy to abuse IMO, and instead add a specific field for the Azure client ID?
There was a problem hiding this comment.
As mentioned above, I would just create a specific flag for the Azure client ID and avoid generic "join params".
There was a problem hiding this comment.
Can we this passed to the installer web API as a parameter that would return the script with proper client ID baked in, instead of environment variable?
There was a problem hiding this comment.
Let's not introduce a custom join params "CLI protocol" with custom parsing format, it will quickly get very messy.
fda6e69 to
df83661
Compare
|
🤖 Vercel preview here: https://docs-2eg5uwx3t-goteleport.vercel.app/docs/ver/14.x |
There was a problem hiding this comment.
| Azure *AzureInstallParams `yaml:"azure"` | |
| Azure *AzureInstallParams `yaml:"azure,omitempty"` |
There was a problem hiding this comment.
I'm probably just missing something but one thing I don't understand is how is this ClientID actually being used to pick the correct Azure identity client? In this PR I see that it's being passed to the install script and then to the join config, but where is it actually being used?
There was a problem hiding this comment.
Lines 697 to 708 in 492e3b3
It's been supported by the Azure join method for a while, this PR just makes it work for discovered nodes too.
|
🤖 Vercel preview here: https://docs-fkg28baez-goteleport.vercel.app/docs/ver/14.x |
This change adds the `client_id` optio nto the Discovery Service for Azure VMs, which sets the client ID of the managed identity for discovered nodes to use when joining the cluster. This allows the discovered nodes to be discovered while having multiple managed identities assigned.
da732ac to
40a30ab
Compare
|
🤖 Vercel preview here: https://docs-c6q2otdkb-goteleport.vercel.app/docs/ver/14.x |
|
🤖 Vercel preview here: https://docs-6a0v4xmmd-goteleport.vercel.app/docs/ver/14.x |
This PR adds the
client_idoption to the Discovery Service for Azure VMs, which sets the client ID of the managed identity for discovered nodes to use when joining the cluster. This allows the discovered nodes to be discovered while having multiple managed identities assigned.Resolves #28839.