keda | based Event Driven Autoscaling component | Serverless library

KEDA scaler not scales with scaled object defined with trigger using pod identity for authentication for service bus queue. I'm following this KEDA service bus triggered scaling project.
The scaling works fine with the connection string, but when I try to scale using the pod identity for KEDA scaler the keda operator fails to get the azure identity bound to it with the following keda operator error message log:

So, I have a Service Bus Queue which is handling two types of messages, for one type of message I want to trigger KEDA however want to restrict KEDA to not instantiate container for other type of message. I can attach properties to the service bus message if that's anyhow it is possible.

I referred https://keda.sh/docs/2.5/scalers/azure-service-bus/ but couldn't find something that's helpful.

Please help if there's a way to do so.

I am trying to create a KEDA scaled job based on RabbitMQ queue trigger but encountered an issue when pods are not scaling at all.

I have created a following Scaled job and lined up messages in the queue but no pods are created. I see this message: Scaling is not performed because triggers are not active

What could be reason that pods are not scaling at all? Thanks for help.

And in Keda logs I see:

I was trying to configure Azure Monitor Scaler for keda autoscaling. In my scaled object I have specified the Clientid and password for the application. In the Azure portal as well, I can see the clientid , password and tenantid . But after deploying the scaledobject , I'm getting error on keda operator like no activeDirectoryClientId given. I don't know what went wrong. Can anyone please help me here?

Below is keda-operator logs:

We have containerized ActiveMQ Artemis 2.16.0 and deployed it as a K8s deployment for KEDA.

We use STOMP using stomp.py python module. The ACK-mode is set as client-individual and consumerWindowSize = 0 on the connection. We are promptly acknowledging the message as soon as we read it.

The problem is, sometimes, the message count in the web console does not become zero even after all the messages are actually consumed and acknowledged. When I browse the queue, I don't see any messages in it. This is causing KEDA to spin up pods unnecessarily. Please refer to the attached screenshots I attached in the JIRA for this issue.

I am using this helm chart to deploy airflow https://github.com/apache/airflow/tree/master/chart

Apache Airflow version: 2.0.0

Kubernetes version: v1.19.4

What happened: I get this error when try to execute tasks using kubernetes

My objective is to be able to deploy airflow on Kubernetes using a custom image (placed in ECR. The reason I want to use this custom Image is because I want to deploy another tool (dbt) with airflow in the same container (also open for other suggestions there)

What actually worked: I have managed to use this Helm chart (which uses the following image as default) to deploy

What I tried to do and did not work: I wanted to now exchange the default image with my custom image in ECR, so I created values.yaml, that contains:

I am trying to deploy Scaledjob of KEDA in AKS. Am getting the below error.

I have deployed Azure Durable Http Triggered Function app in Azure Kubernetes Service. I used Visual Studio Code to create the function app. I have followed instructions from this this article and Microsoft official documentation.