We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened: Workload identity is not working
What you expected to happen: Workload identity should work
How to reproduce it: Try to use workload identity
Anything else we need to know?:
Since this commit: https://github.com/wiz-sec/azuredisk-csi-driver/commit/01b0efc4be6b8963eeff0fcd0c5a35f3edeb5545 workload identity is broken, since ParseConfig is not called anymore and therefore this code part:
if tenantID := os.Getenv("AZURE_TENANT_ID"); tenantID != "" { config.TenantID = tenantID } if clientID := os.Getenv("AZURE_CLIENT_ID"); clientID != "" { config.AADClientID = clientID } if federatedTokenFile := os.Getenv("AZURE_FEDERATED_TOKEN_FILE"); federatedTokenFile != "" { config.AADFederatedTokenFile = federatedTokenFile config.UseFederatedWorkloadIdentityExtension = true }
does not get called anymore.
Environment:
kubectl version
uname -a
The text was updated successfully, but these errors were encountered:
/assign @cvvz
Sorry, something went wrong.
Hi, @AdallomRoy Thanks for your report. I've filed a PR to fix this issue.
cvvz
Successfully merging a pull request may close this issue.
What happened: Workload identity is not working
What you expected to happen: Workload identity should work
How to reproduce it: Try to use workload identity
Anything else we need to know?:
Since this commit: https://github.com/wiz-sec/azuredisk-csi-driver/commit/01b0efc4be6b8963eeff0fcd0c5a35f3edeb5545 workload identity is broken, since ParseConfig is not called anymore and therefore this code part:
does not get called anymore.
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: