Tony Lee

I created a feature request support ticket and my TAM told me that this feature is on planning roadmap to be released in 12+ months, hopefully this feature can be...

Any update ? We are experiencing loopback interface down issue after we introduced KEDA and use jobs to frequently create many short-lived pods to consume msgs, the ugly workaround to...

Our use case is that developers deploy their apps with HPA resource through CICD pipeline, devops team would then use [scheduled-scaler](https://github.com/West-Coast-Devops/scheduled-scaler) to dynamically adjust HPA min/max settings according to the...

Any plan to fix this? k8s-spot-rescheduler has problem with 1.16 or later version

My exclude/include in serverless.yml as below worked well before, ``` package: exclude: - ./** individually: true functions: hello: package: include: - hello/** ``` until I added layers, I got "...

@aravindh-seeneevasan The data ingestion cost of cloudwatch log is much more expensive than the storage, moving log from cloudwatch to s3 can not save much.

Can we use a annotation to specify which annotations or labels need to be propagated without appending suffix `-primary` ?For example: ```yaml annotations: flagger.io/annotations-propagation: , flagger.io/labels-propagation: , ```

We encounter this issue recently, too. Not sure if it's already scheduled in v2.10 release, if not, can we raise the severity of this issue? This issue makes KEDA not...

Experience same issue, from below log I think that cluster-autoscaler would remember all taints on the last node of ASG in memory before scaling down to zero regardless some taints...

We also need our custom labels and annotations being copied for the KEDA scaledObject or all ```*-primary``` resources for our custom validation or mutation