# Kubernetes Baremetal Configuration

**URL:** <https://discuss.elastic.co/t/kubernetes-baremetal-configuration/82030>\
**Category:** Elasticsearch\
**Created:** [April 11, 2017, 6:03pm UTC](https://discuss.elastic.co/t/kubernetes-baremetal-configuration/82030 "2017-04-11T18:03:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![webeindustry](https://avatars.discourse-cdn.com/v4/letter/w/9de053/32.png) [@webeindustry](https://discuss.elastic.co/u/webeindustry)\
**Post date:** [April 11, 2017, 6:03pm UTC](https://discuss.elastic.co/t/kubernetes-baremetal-configuration/82030/1 "2017-04-11T18:03:26Z")

</div>

Hi ES community. I'm trying to run an elasticsearch cluster on my kubernetes bare-metal setup.

I took some inspiration from here: [Running Elasticsearch on Kubernetes](https://vichargrave.github.io/articles/2016-10/running-elasticsearch-on-kubernetes)

& tried to adapt it for my getup, but am not having full success yet.

Please look over my config & let me know where I may be in error. Thank you!

[es-client](https://pastebin.com/VzN5SZtL) | [es-data](https://pastebin.com/zSaaN3MF) | [es-master](https://pastebin.com/SyMrpJ2P) | [es-svc](https://pastebin.com/v6cjKQDr)

I also modified the [elasticsearch.yml config file](https://pastebin.com/0taDXaHm)

When I hit the service address from a pod this results:

```
curl -XGET 'http://elasticsearch.default.svc.kubernetes.local:9200/_cluster/stats?pretty'

{ ... }

 "nodes" : {
"count" : {
  "total" : 1,
  "master_only" : 0,
  "data_only" : 0,
  "master_data" : 0,
  "client" : 0
},

```

Can anyone help point me in the correct direction?

---

<div class="post-metadata">

**Author:** ![webeindustry](https://avatars.discourse-cdn.com/v4/letter/w/9de053/32.png) [@webeindustry](https://discuss.elastic.co/u/webeindustry)\
**Post date:** [April 12, 2017, 12:22am UTC](https://discuss.elastic.co/t/kubernetes-baremetal-configuration/82030/2 "2017-04-12T00:22:41Z")

</div>

I solved the issues on my own. My approach was pretty jacked up, but I had tried vanilla guides to no avail. Turns out one major reason was due to an ongoing (and recently reported) issue surrounding overlay(2)fs and 4+ base images. Built my own image by consolidating the commands of 3 dockerfiles into 1, stored it on my own public repo (with firewalled port), done.

Will make a simple guide later to hopefully help someone out who runs into similar nightmare.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 10, 2017, 12:35am UTC](https://discuss.elastic.co/t/kubernetes-baremetal-configuration/82030/3 "2017-05-10T00:35:20Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.