I got nothing on health - kibaba

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

Hi,
I have another question:
I whant to build a ELK Cluster on kubernetes cluster on button8 namespace, thw cluster should include 1 Elasticsearch, 1 Kibana
so, I ran:

helm repo add elastic https://helm.elastic.co
helm repo update

and then

helm install elastic-operator elastic/eck-operator -n button8 --create-namespace
and then I created an Elasticsearch:

apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: cdbridgerpayelasticsearch
spec:
  version: 7.6.2
  nodeSets:
  - name: default
    count: 1
    config:
      node.master: true
      node.data: true
      node.ingest: true
      node.store.allow_mmap: false

and it ran well:

$ kubectl get elasticsearch -n default
W0613 15:29:08.043023 906 gcp.go:120] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead.
To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
NAME HEALTH NODES VERSION PHASE AGE
bcdbridgerpayelasticsearch green 1 7.6.2 Ready 43m

now

I created a Kibaba:

apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: bcdkibaba
spec:
  version: 7.6.2
  count: 1
  elasticsearchRef:
    name: cdbridgerpayelasticsearch

but when I ran It- there was nothing in the health colum:

$ kubectl get kibana
W0613 15:36:38.025142 986 gcp.go:120] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead.
To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
NAME HEALTH NODES VERSION AGE
bcdkibaba 6m10s

why is it?
Do I need to deploy the Elasticsearch and the Kibaba in the button8 ns?
(because I tried to create the Elasticsearch there and I got: HEALTH -unknown,
so now mMy Elasticsearch is in the default ns)

thanks
Frida

2

We have a list of troubleshooting tips here. I would start with looking at the operator logs to find out what is going on:

If that does not help I would check how far the operator got with rolling out Kibana. Is there a deployment for Kibana for example, are there maybe even Pods running. If yes have they any errors in their status for example.

3

Thank you very much!!!!!!

4

If possible... :smiling_face:
I have another question:

thanks!!!!!
:star_struck:

5

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