-
Notifications
You must be signed in to change notification settings - Fork 56
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
Unable to use Azure Workload Identity, AZURE_CLIENT_ID and AZURE_TENANT_ID are overritten by chart. #1304
Comments
I took a brief look at the PR, and it looks OK, but before we move forward, could you pls explain a bit more what the use case is? I haven't fully understood it. Is this because some Azure deployment mechanism writes the same env vars ( |
Hello, sure :) Generally EDC updated the Azure libraries that allows Azure Federated Credential authorization with use of managed identities. This is automatic mechanism for Azure to authorize without any secrets and is fully managed by Kubernetes webhook. https://learn.microsoft.com/en-us/azure/aks/workload-identity-overview The problem there is, that tractus-x with update to 0.7.0 changed Azure authentication variables from EDC_VAULT_CLIENTID, EDC_VAULT_TENANTID to AZURE_CLIENT_ID and AZURE_TENANT_ID (source, point 6). Charts are overriding the variables that are created automatically via workload identity webhook. |
ok got it. Just for the sake of completeness, this example shows the goings-on best I think. |
Describe the bug
While deploying EDC using "tractusx-connector-azure-vault" on Azure utilizing workload identity, charts are overriding the values that are attached automatically by Azure webhook.
To Reproduce
Try to deploy EDC using tractusx-connector-azure-vault chart.
Expected behavior
Variables should be optional to allow for webhook to be attached properly.
Screenshots/Error Messages
Cause:
Actual behaviour:
Expected behaviour:
Context Information
n/a
Possible Implementation
Make variables "AZURE_CLIENT_ID" and "AZURE_TENANT_ID" optional.
The text was updated successfully, but these errors were encountered: