-
Notifications
You must be signed in to change notification settings - Fork 93
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
kubelogin get-token
timeout is not configurable
#223
Comments
@weinong Can you please check? |
as pointed out by @Bondza signal killed source is: azure-sdk-for-go/sdk/azidentity It looks like the value of ten seconds has been hardcoded since the first commit to azidentity
Feature request Azure/azure-sdk-for-go#21985 Its configurable in the python sdk
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
We have a use case where we use multiple kubeconfig files configured to use
kubelogin get-token --login azurecli
, and these configuration files are used concurrently.With this configuration
kubelogin
will callaz account get-access-token
. The latest release ofkubelogin
(v0.0.27) usesgithub.com/Azure/azure-sdk-for-go/sdk/azidentity
v1.1.0, this version ofazidentity
hardcodes a timeout of 10 seconds when callingaz
.We call
kubectl
concurrently with multiple different kubeconfig files configured to usekubelogin
. This results inaz
occasionally taking longer than 10 seconds to get an access token. When this happenskubelogin
fails with the following error message:If the timeout was configurable through a
--timeout
option or similar it would allow us to giveaz
more time to retrieve the access token which might help avoiding this issue.The text was updated successfully, but these errors were encountered: