Problem with Kibana creation and roles on Elasticsearch nodes

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

HI all,

First post so be patient with me :slight_smile:

So let the music pay on ...

I've created an Elasticsearch cluster with ECK version 2.5 no problem during Elasticsearch creation with the following manifest

apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: preprod
  namespace: elastic-system
spec:
  version: 8.5.0
  nodeSets:
  - name: "master"
    count: 3
    config:
      node.roles: ["master"]
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 4Gi
        storageClassName: lyo0-oc5k-nfs
  - name: ingest
    count: 3
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data # Do not change this name unless you set up a volume mount for the data path.
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 4Gi
        storageClassName: lyo0-oc5k-nfs
    config:
      node.roles: ["ingest"]
  - name: data-hot
    count: 3
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data # Do not change this name unless you set up a volume mount for the data path.
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 16Gi
        storageClassName: lyo0-oc5k-nfs
    config:
      node.roles: ["data_hot"]
  - name: data-warm
    count: 3
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data # Do not change this name unless you set up a volume mount for the data path.
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 32Gi
        storageClassName: lyo0-oc5k-nfs
    config:
      node.roles: ["data_warm"]

But when I create a kibana instance with the following manifest

apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: preprod
  namespace: elastic-system
spec:
  version: 8.5.0
  count: 1
  elasticsearchRef:
    name: preprod
    namespace: elastic-system
  http:
    tls:
      selfSignedCertificate:
        disabled: true
  config:
    server.publicBaseUrl: https://xxxxx.xxxx.xxxx.sample.com

Elasticsearch go to red status and the only way to retrieve the green status for my Elastic cluster is to assign the data role to nodes master and ingest.

Is it normal ?

Thanks by advance for your replies.

2

OK for those who read this tread after opening an issue on ECK Github I've the solution :

the role data_content is missing on at least one node. So on the previous manifest I've added the data_content role on nodesets data-hot and data-warm which solved the issue.

Regards

3

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