# Error with ECK Operator 2.3.0 - Failed to get API Group-Resources

**URL:** <https://discuss.elastic.co/t/error-with-eck-operator-2-3-0-failed-to-get-api-group-resources/312674>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [August 23, 2022, 6:32am UTC](https://discuss.elastic.co/t/error-with-eck-operator-2-3-0-failed-to-get-api-group-resources/312674 "2022-08-23T06:32:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:43pm UTC](https://discuss.elastic.co/t/error-with-eck-operator-2-3-0-failed-to-get-api-group-resources/312674/2 "2022-08-24T12:43:34Z")

</div>

The ECK operator exits because it fails to connect to the Kubernetes API server. I assume you are proxying these connections with Istio? If so, I would start looking on the Istio side why the connections are being blocked, are the proxies healthy? or are these genuine failures of the Kubernetes control plane then I would start looking into the health of the Kubernetes API server. You posted a similar question about failed leader elections here [ECK Operator - Leader Election Lost causes Restart - #2 by pebrc](https://discuss.elastic.co/t/eck-operator-leader-election-lost-causes-restart/312677/2) that points to the same underlying problem.

---

_[View the full topic](https://discuss.elastic.co/t/error-with-eck-operator-2-3-0-failed-to-get-api-group-resources/312674)._