Jorge Turrado Ferrero

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

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

@dttung2905 @zroubalik , WDYT?

I guess that we can continue with the current implementation without adding the support to the experimental, as after the last community call we plan to deprecate and remove the...

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

Thanks for the contribution!

Hey! Are you asking about HTTP based autoscaling? If yes, I'd suggest checking this the HTTP Add-on: https://github.com/kedacore/http-add-on

It depends on how you do it, if you want to call the FQDN directly using the add-on, you should configure the add-on to proxy that host (in hosts section)...

For example, [this e2e test ](https://github.com/kedacore/http-add-on/blob/main/tests/checks/internal_service/internal_service_test.go)covers that scenario: `command: ["curl", "-H", "Host: {{.Host}}", "keda-http-add-on-interceptor-proxy.keda:8080"]` Basically, it calls directly to interceptor service but setting the host header with the value of...

Hello, You can find more info here: https://keda.sh/blog/2023-05-02-certificate-improvements/ We removed the `insecureSkipTLSVerify: true` in favor of managed certificates. There are 3 working ways: - KEDA manages its own certificate -...