Jorge Turrado Ferrero

@zroubalik , any idea?

>Is there any way to write profiling data outside pod. So we can visualize even after pod restart It's not possible to profile KEDA if it dies automatically just after...

The network activity is between the operator and internet or between the KEDA components? the problem isn't v2.13 but 2.12 as far as I understand, right?

I'm checking and there is a big important change between 2.11 and 2.12 related with the SDK https://github.com/kedacore/keda/commit/791c895bf53984220bef9981e161cf00d5fcc9ee because we changed the SDK v1 to the SDK v2, but it's...

At this point, and not having any way to extract the pprof info, the only option that I can offer is debugging it locally. You can use your current cluster...

/run-e2e **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/8590443390)

@bharathguvvala , could you check the failing CI checks? I think that unit tests probably need to be updated as they expect the call to `patch`

Hello @Frezyy123 I think that having more control over the fallback, it's an interesting scenario to go deeper. I don't know how can we design this for being more flexible...

@tomkerkhove @zroubalik WDYT? About the proposal, I'd move the `skipFailing` property from metadata to the trigger spec directly

I think that it's a good moment to unify all the loggers across components, operator uses zap IIRC, maybe can give a try but I think that custom-metrics-apiserver can be...