# ECK Operator - Leader Election Lost causes Restart **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [August 23, 2022, 6:42am UTC](https://discuss.elastic.co/t/eck-operator-leader-election-lost-causes-restart/312677 "2022-08-23T06:42:59Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\ **Post date:** [August 24, 2022, 12:33pm UTC](https://discuss.elastic.co/t/eck-operator-leader-election-lost-causes-restart/312677/2 "2022-08-24T12:33:20Z")
I am not sure what is the cause of your issue. But the error you quoted makes me wonder if you Kubernetes cluster is healthy. Do other requests to the API server let's say with `kubectl` succeed any other indications that the Kubernetes control plane is unhealthy? > Get "[https://10.0.0.1:443/api/v1/namespaces/elastic-system/configmaps/elastic-operator-leader?timeout=1m0s](https://10.0.0.1:443/api/v1/namespaces/elastic-system/configmaps/elastic-operator-leader?timeout=1m0s)": context deadline exceeded --- _[View the full topic](https://discuss.elastic.co/t/eck-operator-leader-election-lost-causes-restart/312677)._