vickithedeveloper

@v-shenoy Today we tried the method you suggested above. But the error was still present. Hence we redeployed the original code and the "blob not found" error is not coming...

@v-shenoy I am using connection strings in the scaled object. When I ran the command "kubectl get --raw "/apis/external.metrics.k8s.io/v1beta1" , I got the below output. **{"kind":"APIResourceList","apiVersion":"v1","groupVersion":"external.metrics.k8s.io/v1beta1","resources":[{"name":"s0-azure-eventhub-$Default","singularName":"","namespaced":true,"kind":"ExternalMetricValueList","verbs":["get"]}]}** From the following command...

The issue is resolved partially by commenting the "aadpodidbinding" label as shown below in the deployment file below. Now KEDA is able to scale the function app. Following are the...

I was continuing my testing today on the same code as in the previous comment and observed following issues - 1. Today I tested the code with the AAD pod...

@christle The "BlobNotFound" is present in the actual error. it has not been modified. In the title, the blob name is replaced with dummy value. Regarding consumer group , we...

@christle @v-shenoy In the documentation it says that "The Azure Storage connection string is not compatible with connection string created from a Shared Access Signature." Could you please share the...

@christle I rechecked it and error messages is having the following pattern - GET https://staccoutnname.blob.core.windows.net/azure-webjobs-eventhub/namespace.servicebus.windows.net/eh-name/consumerGroupName/checkpoint/ Also I can confirm that even in my deployment , we are using the same...

@Christle The issue is resolved by upgrading the storage account the premium and changing the storage account to have the blob configuration. Earlier the storage account was having ADLS2 configuration.