Self-signed cert errors for keda-operator-metrics-apiserver about keda HOT 3 CLOSED

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
• cert-manager integration
• You manage them by your side

For the first option, KEDA operator generates a secret within the namespace where the operator is which contains the TLS certificate generated and managed by KEDA. Once the certificate is ready, it restarts itself and during the next startup it'll patch the apiservice's caBundle with the cert CA.
For the second option, you can use the cert-manager integration using KEDA's chart, which basically will do the same as the 1st option but the cert will be created and managed by cert-manager and it's cert-manager who patches the apiservice.
For the last option, you can mount your own certs but you are the responsible of patching all the resources which require trusting in KEDA (apiservice, webhooks, etc).

Do you see the secret with the certs in the namespace where KEDA is? Do you see any error in KEDA operator logs?

from keda.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

from keda.

This issue has been automatically closed due to inactivity.

from keda.