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
Context Canceled with Azure Managed Identity #3296
Comments
What happens when you downgrade the aad-pod-identity helm chart? We have seen similar flavoured but different issues since last Friday (24. June 2022) unrelated to Azure Managed Identities |
So when we use aad-pod-identity helm chart at version 4.1.8, this works fine but the issue began with chart version 4.1.10. Others are also reporting time out issues at the token retrieval with pod identity when using a similar setup as KEDA with azure Azure/aad-pod-identity#1287 |
Just tested a downgrade of aad-pod-identity helm chart and still getting same error. |
Just assume for a second this error is unrelated to the Helm chart. When did you see this error for the first time? I'm trying to pinpoint the source of the issue and somehow I get the feeling that Azure might be the source. |
Are there any errors in aad-pod-identity pods? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Upgraded our cluster aad-pod-identity helm chart to 4.1.10 and we are now getting the following error when trying to use an Azure Queue Scaled Job with Keda:
This same managed identity worked with the same permissions before until we upgraded and it seems like it might be a permission timeout but not too sure.
Expected Behavior
The Keda operator should be able to read the Azure queue and scaled up our application pods to handle the objects in the queue.
Actual Behavior
Keda operator fails with a context canceled error when running ScaledJob.
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: