-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Crashes read/write/backend using Azure blob with AAD workload identity. #9952
Comments
Additional info: There has a Cert-manager with AAD workload identity in the same AKS cluster. |
I have no issues writing to an Azure storage account with AAD Workload Identity with the configuration below. Are annotations configured on the serviceAccount? I would also double check the federated credentials/role assignments is properly configured on Azure.
|
I have the same issue with one of my subscriptions. For some reason the company subscription I got a runtime error. Env. K8s. ver: 1.26.6 Loki App ver: 2.8.2 `panic: runtime error: invalid memory address or nil pointer dereference goroutine 1 [running]: |
I noticed the same issue today after updating to the latest version of loki-distributed chart because we wanted to use workload identity instead of pod identity. In our case, the issue was quickly solved because I noticed the |
I have the same problem. @monaka did you find any solution? |
same here |
Describe the bug
I tried to use Azure blob with AAD workflow identity.
I got errors on read/write/backend.
To Reproduce
CrashLoopBackoff
.Expected behavior
All components are booted up and moving to
Running
.Environment:
Screenshots, Promtail config, or terminal output
The text was updated successfully, but these errors were encountered: