-
Notifications
You must be signed in to change notification settings - Fork 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
keda operator restarted at the time of start.(error retrieving resource lock keda/operator.keda.sh) #2836
Comments
This is most likely a problem in |
I've found this. What puzzles me is that I saw the same error message ("failed to renew lease" ) on the other controllers in the cluster that probably use |
Hard to say, could please try to tweak those settings on your setup? |
@crisp2u @zroubalik Where exactly do we need to tweak values? |
I'm also seeing this issue, and it's leading to noisy pod restart alerts in our AKS cluster. We are only running 1 replica of the KEDA operator, but as of now we're seeing container restarts ~3-8 times a day thanks to
@zroubalik - Presumably you were talking previously about tweaking the lease-related settings? Perhaps there should be a hook in the helm chart for configuring the leasing options: Lines 87 to 95 in dcb9c1e
|
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. |
This issue has been automatically closed due to inactivity. |
Discussed in #2722
Originally posted by vkamlesh March 7, 2022
Keda operator failed to elect leader after keda-operator pod restart. These restarts are not frequent but it's happening in a few days(6 days) time intervals.
KEDA Version: 2.6.1
Git Commit: efca71d
Kubernetes version: v1.20.9
Kubernetes Cluster : AKS
The text was updated successfully, but these errors were encountered: