# Eck unable to form a cluster **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [January 30, 2023, 12:41pm UTC](https://discuss.elastic.co/t/eck-unable-to-form-a-cluster/324229 "2023-01-30T12:41:06Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![charlot\_Attard](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@charlot\_Attard](https://discuss.elastic.co/u/charlot_Attard)\ **Post date:** [January 30, 2023, 12:41pm UTC](https://discuss.elastic.co/t/eck-unable-to-form-a-cluster/324229/1 "2023-01-30T12:41:06Z")
Hello, I am tshooting an issue which was escalated by devs. Currently we have a 3 node eck cluster. The problem is that on the pod logs of elastic we are getting this message "Discovery will continue using 127.0.0.1:9300,127.0.0.1:9301 from last-known cluster state; " The seed\_providers is file and is populated and available as I checked. Any idea what this can be ? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 31, 2023, 4:46am UTC](https://discuss.elastic.co/t/eck-unable-to-form-a-cluster/324229/2 "2023-01-31T04:46:54Z")
It'd be useful if you shared your config and the full log. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 28, 2023, 4:47am UTC](https://discuss.elastic.co/t/eck-unable-to-form-a-cluster/324229/3 "2023-02-28T04:47:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.