Closed Mithgroth closed 9 months ago
It looks like you're using the azureQueue
scaler, which is for Azure Storage queues, not Azure Service Bus. See this doc for information on how to configure an ASB rule: https://learn.microsoft.com/en-us/azure/container-apps/scale-app?pivots=azure-resource-manager#example-2
Thanks, it works as intended now.
This issue is a: (mark with an x)
Issue description
I have a .NET 8.0 console application in a container, which is deployed to ACR and run on ContainerApps. Application is built on MassTransit, uses Azure Service Bus queues. It works great, but I always have one active replica running even there are no requests at all.
I tried it both ways with having my scaling rules with queue and connection, no change at all.
Unlike #952, I have no key-vault references, my secrets are Container Apps Secrets.
Here's the JSON of my resource:
Steps to reproduce
Expected behavior [What you expected to happen.] Container replicas scaling down to 0 after cool down period
Actual behavior [What actually happened.] 1 container is always up
Screenshots
If applicable, add screenshots to help explain your problem. 7+ minutes in, container is still alive.
Additional context
Ex. Did this issue occur in the CLI or the Portal? Portal