# Helm3 chart version v7.9.1 Elasticsearch and Kibana both on the same Minikube profile

**URL:** <https://discuss.elastic.co/t/helm3-chart-version-v7-9-1-elasticsearch-and-kibana-both-on-the-same-minikube-profile/248655>\
**Category:** Elasticsearch\
**Created:** [September 15, 2020, 10:30am UTC](https://discuss.elastic.co/t/helm3-chart-version-v7-9-1-elasticsearch-and-kibana-both-on-the-same-minikube-profile/248655 "2020-09-15T10:30:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![vugar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vugar/32/75587_2.png) [@vugar](https://discuss.elastic.co/u/vugar)\
**Post date:** [September 15, 2020, 10:30am UTC](https://discuss.elastic.co/t/helm3-chart-version-v7-9-1-elasticsearch-and-kibana-both-on-the-same-minikube-profile/248655/1 "2020-09-15T10:30:48Z")

</div>

Hi there!

Anyone had any luck with deploying both Elasticsearch and Kibana on the same Minikube profile with Helm3 ? It seems as if I can deploy only Elasticsearch or Kibana but not both...

---

<div class="post-metadata">

**Author:** ![Julien\_MAILLERET](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julien_mailleret/32/45074_2.png) [@Julien\_MAILLERET](https://discuss.elastic.co/u/Julien_MAILLERET)\
**Post date:** [September 16, 2020, 7:15am UTC](https://discuss.elastic.co/t/helm3-chart-version-v7-9-1-elasticsearch-and-kibana-both-on-the-same-minikube-profile/248655/2 "2020-09-16T07:15:17Z")

</div>

Hi @vugar,  
Can you provide more details:

- What charts are you using to deploy Elasticsearch and Kibana?
- Post your values files
- Post your install commands and logs

---

<div class="post-metadata">

**Author:** ![vugar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vugar/32/75587_2.png) [@vugar](https://discuss.elastic.co/u/vugar)\
**Post date:** [September 16, 2020, 8:32am UTC](https://discuss.elastic.co/t/helm3-chart-version-v7-9-1-elasticsearch-and-kibana-both-on-the-same-minikube-profile/248655/3 "2020-09-16T08:32:15Z")

</div>

Thank you for looking into this @Julien_MAILLERET

Nothing fancy really, just started my minikube profile:

> minikube start --profile='elastic-fancy' --kubernetes-version=v1.18.8 --driver=kvm2 --memory='8192' --cpus='2' --disk-size=30

Please correct me if I am wrong but as I understand following should result in Elasticsearch and Kibana both running on the same Minikube profile.

> helm repo add elastic [https://helm.elastic.co](https://helm.elastic.co)  
> helm repo update

> helm install elasticsearch elastic/elasticsearch --values '[https://github.com/elastic/helm-charts/raw/7.9.1/elasticsearch/examples/minikube/values.yaml](https://github.com/elastic/helm-charts/raw/7.9.1/elasticsearch/examples/minikube/values.yaml)'

> helm install kibana elastic/kibana --set elasticsearchHosts='[http://elasticsearch-master.svc.cluster.local:9200](http://elasticsearch-master.svc.cluster.local:9200)'

And I end up with Kibana pod stuck in 'pending' state

> kubectl get pods --namespace=default -l app=kibana -w  
> NAME READY STATUS RESTARTS AGE  
> kibana-kibana-55fc8f9f4f-8xvcm 0/1 Pending 0

Mind you though I can connect (to Elasticsearch deployed to the same minikube profile) my external (running outside of minikube profile) Kibana just fine - though I have to note that default 'kibana.yml' provided in the original docker image was also resulting in Kibana failing almost immediately after start, so I had to modify it a bit...

Please let me know if there is any further info might be required!

---

<div class="post-metadata">

**Author:** ![Julien\_MAILLERET](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julien_mailleret/32/45074_2.png) [@Julien\_MAILLERET](https://discuss.elastic.co/u/Julien_MAILLERET)\
**Post date:** [September 16, 2020, 12:59pm UTC](https://discuss.elastic.co/t/helm3-chart-version-v7-9-1-elasticsearch-and-kibana-both-on-the-same-minikube-profile/248655/4 "2020-09-16T12:59:23Z")

</div>

The good format for K8S service is `my-svc.my-namespace.svc.cluster-domain.example` (source: [A/AAAA records](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#a-aaaa-records)). I think you forgot the namespace part in your `elasticsearchHosts` URL.

---

<div class="post-metadata">

**Author:** ![vugar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vugar/32/75587_2.png) [@vugar](https://discuss.elastic.co/u/vugar)\
**Post date:** [September 17, 2020, 4:09am UTC](https://discuss.elastic.co/t/helm3-chart-version-v7-9-1-elasticsearch-and-kibana-both-on-the-same-minikube-profile/248655/5 "2020-09-17T04:09:12Z")

</div>

Thank you @Julien_MAILLERET!

Always nice to have a second pair of eyes! 🙂 Indeed missed the namespace, though I am quite certain I've seen similar issue on different namespaces as well - and these were supplied as a service FQDN.

In any case just did a re-deploy of both Elasticsearch and Kibana to 'default' and repeated on non-default namespaces - it seems as if everything working as it should!

---

<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:** [October 15, 2020, 4:09am UTC](https://discuss.elastic.co/t/helm3-chart-version-v7-9-1-elasticsearch-and-kibana-both-on-the-same-minikube-profile/248655/6 "2020-10-15T04:09:19Z")

</div>

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