Using own certicates - Error tls: bad certificate

[pacmanmulet]

secret.zip

Report

We are encountering an error when using our own certificates.

Expected Behavior:

Metrics server successfully connected to operator

Actual Behavior

Steps to reproduce the problem

1. Create kedaorg-certs secret using attached secret with a testing certificate data:

2. Install Keda chart to your cluster (Using 2.14.2 chart version) disabling certs:

certificates:
  autoGenerated: false

KEDA version
2.14.0

Kubernetes Version
1.27.0

Is it possible that this specific certificate type is incompatible with the solution? In that case, what configuration is supported in the certificate?

That is a summary of his section 509v3 extensions:

            X509v3 Subject Alternative Name: 
                DNS:keda-operator, DNS:keda-operator.keda, DNS:keda-operator.keda.svc, DNS:keda-operator.keda.svc.cluster.local, DNS:keda-admission-webhooks, DNS:keda-admission-webhooks.keda, DNS:keda-admission-webhooks.keda.svc, DNS:keda-admission-webhooks.keda.svc.cluster.local, DNS:keda-operator-metrics-apiserver, DNS:keda-operator-metrics-apiserver.keda, DNS:keda-operator-metrics-apiserver.keda.svc, DNS:keda-operator-metrics-apiserver.keda.svc.cluster.local
            X509v3 Subject Key Identifier: 
                ...
            X509v3 Authority Key Identifier: 
                ...
            X509v3 CRL Distribution Points: 
                Full Name:
                  URI: XXX
                  URI: XXX
            Authority Information Access: 
                CA Issuers - URI:XXX
                CA Issuers - URI:XXX
                OCSP - URI:XXX
            X509v3 Key Usage: 
                Digital Signature, Key Encipherment
            1.3.6.1.4.1.311.21.7: 
                ...
            X509v3 Extended Key Usage: 
                TLS Web Server Authentication
            1.3.6.1.4.1.311.21.10: 
                0.0

Thanks.

[pacmanmulet]

Need MTLS certificate