-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error updating webhook with certificate {"error": "Operation cannot be fulfilled on apiservices.apiregistration.k8s.io \"v1beta1.external.metrics.k8s.io\": the object has been modified; please apply your changes to the latest version and try again"} #6551
Comments
Hello |
Hello @JorTurFer ,
I found when keda-operator kept reporting this error per 6 minutes, keda-metrics-api-server will be failed to connect to keda-operator, and service been affected in terms of scaling. We need to restart keda-operator to let it back to normal, thanks. I'm trying to disable cert rotation and see if we'll encounter the issue again, thanks.
|
if you're deploying KEDA using helm chart and you use cert-manager in your cluster too, you can delegate the certificate management to cert-manager (which is the best idea if you are already using KEDA's helm chart and cert-manager) |
No, we didn't deploy cert-manager in our cluster. But I still think it's part of issue on keda-operator, can you help check? We've disabled cert-rotation for now, it works as expect for at least 5 days... |
There is nothing that we can do because the error is related with the object being modified at the same time as other (are you using ArgoCD/Flux syncing the chart?) 2025-02-14T22:40:21Z ERROR Reconciler error {"controller": "cert-rotator", "object": {"name":"kedaorg-certs","namespace":"keda"}, "namespace": "keda", "name": "kedaorg-certs", "reconcileID": "7367f7ca-aee4-4c85-a227-2b183d48eeab", "error": "Operation cannot be fulfilled on apiservices.apiregistration.k8s.io \"v1beta1.external.metrics.k8s.io\": the object has been modified; please apply your changes to the latest version and try again"} Once the operator starts, that process doesn't stop the communication between metrics server and the operator AFAIK. That failing process can stop the startup but not the process ongoing. You can keep it disabled if you want because the signed certificate is for 10 years, so if you don't change it, you won't see any issue in the future |
We have argoCD in our cluster, but we didn't maintain core keda component with argoCD. |
Hello! |
Report
Hi support,
we upgraded our keda to 2.16 on 13 Feb 2025 with keda helm-chart ,
and found keda-operator would stop providing service if encounter cert-rotation issue.
didn't catch the keda-metrics-api-server log, but just error that cannot establish connection with keda-operator.
[hpa events]
Expected Behavior
keda-operator can rotate the cert successfully and provide service
Actual Behavior
keda-operator failed to rotate the cert and stop working, keda-metrics-api-server was affected.
Steps to Reproduce the Problem
We just wait for one day, and we'll encounter issue on cert-rotation
Logs from KEDA operator
KEDA Version
2.16.1
Kubernetes Version
< 1.29
Platform
Amazon Web Services
Scaler Details
AWS SQS scaler, prometheus scaler
Anything else?
NA
The text was updated successfully, but these errors were encountered: