You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by pacmanmulet December 19, 2024
Report
We are encountering an error when using our own certificate.
Expected Behavior kubectl get --raw "/apis/external.metrics.k8s.io/v1beta1" works as usual
Actual Behavior
"Error from server (ServiceUnavailable): the server is currently unable to handle the request"
Steps to reproduce the problem
Generate ca and cert files
Create kedaorg-certs secret
Install Keda to your cluster (Using 2.14.2 chart version) disabling certs:
certificates:
autoGenerated: false
KEDA version
2.14.0
Kubernetes Version
1.27.0
Executing the next patch solves the problem, but I suppose it is not the right way: oc patch apiservice v1beta1.external.metrics.k8s.io -p '{"spec": {"insecureSkipTLSVerify": true}}'
Are steps right or there any other requirements for using your own certificate?
Thanks.
The text was updated successfully, but these errors were encountered:
Discussed in #6432
Originally posted by pacmanmulet December 19, 2024
Report
We are encountering an error when using our own certificate.
Expected Behavior
kubectl get --raw "/apis/external.metrics.k8s.io/v1beta1" works as usual
Actual Behavior
"Error from server (ServiceUnavailable): the server is currently unable to handle the request"
Steps to reproduce the problem
Generate ca and cert files
Create kedaorg-certs secret
Install Keda to your cluster (Using 2.14.2 chart version) disabling certs:
KEDA version
2.14.0
Kubernetes Version
1.27.0
Executing the next patch solves the problem, but I suppose it is not the right way:
oc patch apiservice v1beta1.external.metrics.k8s.io -p '{"spec": {"insecureSkipTLSVerify": true}}'
Are steps right or there any other requirements for using your own certificate?
Thanks.
The text was updated successfully, but these errors were encountered: