# Elasticsearch discovery issues kubernetes

**URL:** <https://discuss.elastic.co/t/elasticsearch-discovery-issues-kubernetes/311465>\
**Category:** Elasticsearch\
**Created:** [August 5, 2022, 3:05am UTC](https://discuss.elastic.co/t/elasticsearch-discovery-issues-kubernetes/311465 "2022-08-05T03:05:28Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [August 9, 2022, 6:41am UTC](https://discuss.elastic.co/t/elasticsearch-discovery-issues-kubernetes/311465/5 "2022-08-09T06:41:25Z")

</div>

As Mark says we can only guess at the problem from a vague description of what you're seeing that you think to be relevant.

One possible guess is [this situation](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-bootstrap-cluster.html#modules-discovery-bootstrap-cluster-joining). If that describes what you're seeing then you can use the remedy in the docs:

> If you intended to form a new multi-node cluster but instead bootstrapped a collection of single-node clusters...

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-discovery-issues-kubernetes/311465)._