You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically, We are observing an issue with our Node.js Azure Function App deployed on an AKS cluster.
App intermittently fails to process some files due to missing blob scans on the source storage accounts.
As a result, the Azure Function is not activating for some of these files which is deployed on AKS Cluster.
Setup: The function is hosted in an AKS Cluster and deployed as part of a POD, which is running without issues. Configuration: The setup does not use an Azure Function App resource; everything is deployed on the AKS cluster. Issue : why the Azure function app is missing few files while scanning in the storage account.
Environment:
AKS Cluster
The text was updated successfully, but these errors were encountered:
Hi @Srini-JbAW are you still facing issues? Is this reproducible locally or does it just happen in prod?
If you're able to repro this locally, could you provide a minimal repro (link to repository with the function app code) and share the steps of how you deploy your cluster (using helm?).
If you are only able to repro this in prod, could you open a support ticket for further investigation? Thanks!
Basically, We are observing an issue with our Node.js Azure Function App deployed on an AKS cluster.
App intermittently fails to process some files due to missing blob scans on the source storage accounts.
As a result, the Azure Function is not activating for some of these files which is deployed on AKS Cluster.
Setup: The function is hosted in an AKS Cluster and deployed as part of a POD, which is running without issues.
Configuration: The setup does not use an Azure Function App resource; everything is deployed on the AKS cluster.
Issue : why the Azure function app is missing few files while scanning in the storage account.
Environment:
AKS Cluster
The text was updated successfully, but these errors were encountered: