# Kibanas is stuck after elasticsearch cluster is ready

**URL:** https://discuss.elastic.co/t/kibanas-is-stuck-after-elasticsearch-cluster-is-ready/345546
**Category:** Elastic Cloud on Kubernetes (ECK)
**Created:** [October 23, 2023, 7:33am UTC](https://discuss.elastic.co/t/kibanas-is-stuck-after-elasticsearch-cluster-is-ready/345546 "2023-10-23T07:33:17Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![expert1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/expert1/32/126753_2.png) [@expert1](https://discuss.elastic.co/u/expert1)
#### Post date: [October 23, 2023, 7:33am UTC](https://discuss.elastic.co/t/kibanas-is-stuck-after-elasticsearch-cluster-is-ready/345546/1 "2023-10-23T07:33:17Z")

</div>

Hi, I'm using ECK 2.9. Here are my es and kibana YAML respectively.

```auto
---
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: ealsticsearch
spec:
  version: 7.17.14
  volumeClaimDeletePolicy: DeleteOnScaledownAndClusterDeletion
  podDisruptionBudget:
    spec:
      minAvailable: 2
      selector:
        matchLabels:
          elasticsearch.k8s.elastic.co/cluster-name: ealsticsearch

  http:
    service:
      spec:
        type: ClusterIP
        ports:
        - name: https
          port: 9200
          targetPort: 9200
          protocol: TCP
    tls:
      selfSignedCertificate:
        disabled: true
      certificate:
        # provide your own certificate
        secretName: pt-ssl

  nodeSets:
  - name: default
    count: 3

    podTemplate:
      spec:
        securityContext:
          runAsUser: 1234
          fsGroup: 1234

        initContainers:
        - name: sysctl
          securityContext:
            privileged: true
            runAsUser: 0
          command: ['sh', '-c', 'sysctl -w vm.max_map_count=262144']

        containers:

        - name: elasticsearch
          env:
            - name: PRE_STOP_ADDITIONAL_WAIT_SECONDS
              value: "5"
            - name: READINESS_PROBE_TIMEOUT
              value: "10"
            - name: ES_JAVA_OPTS
              value: "-Xms1g -Xmx1g"

          readinessProbe:
            exec:
              command:
              - bash
              - -c
              - /mnt/elastic-internal/scripts/readiness-probe-script.sh
            failureThreshold: 3
            initialDelaySeconds: 10
            periodSeconds: 12
            successThreshold: 1
            timeoutSeconds: 12

          resources:
            requests:
              memory: 2Gi
              cpu: 2
            limits:
              memory: 2Gi

    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: 5Gi
        storageClassName: rook-ceph-block

```

// kibana.yml

```auto
apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: elasticsearch
spec:
  version: 7.17.14
  count: 1
  elasticsearchRef:
    name: elasticsearch

  http:
    tls:
      selfSignedCertificate:
        disabled: true
      certificate:
        # provide your own certificate
        secretName: pt-ssl

```

After ES cluster are ready, I apply kibana.yml and find it's stuck with the following messages.

```auto
Name: elasticsearch
Namespace: elasticsearch
Labels: <none>
Annotations: <none>
API Version: kibana.k8s.elastic.co/v1
Kind: Kibana
Metadata:
  Creation Timestamp: 2023-10-23T07:23:43Z
  Generation: 1
  Resource Version: 3267908
  UID: 80f11259-2c30-49bb-81ef-75987799ed25
Spec:
  Count: 1
  Elasticsearch Ref:
    Name: elasticsearch
  Http:
    Tls:
      Certificate:
        Secret Name: pt-ssl
      Self Signed Certificate:
        Disabled: true
  Version: 7.17.14
Status:
  Association Status: Pending
  Count: 0
  Elasticsearch Association Status: Pending
  Observed Generation: 1
Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Warning AssociationError 115s (x3 over 115s) kibana-controller Association backend for elasticsearch is not configured
  Normal AssociationStatusChange 115s kb-es-association-controller Association status changed from [] to [Pending]

```

I searched a while and all posts showed changing YAML of elasticsearch like below

```auto
  http:
    service:
      spec:
        type: ClusterIP
        ports:
        - name: https
          port: 9200
          targetPort: 9200
          protocol: TCP

```

However, mine has these parts already. Turns out it does not work.

There is nothing value in the operator log, either.  
Please help, thanks

---

<div class="post-metadata">

### Author: ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)
#### Post date: [October 23, 2023, 10:05am UTC](https://discuss.elastic.co/t/kibanas-is-stuck-after-elasticsearch-cluster-is-ready/345546/2 "2023-10-23T10:05:28Z")

</div>

> [@expert1](#):
>
> ```auto
> apiVersion: elasticsearch.k8s.elastic.co/v1
> kind: Elasticsearch
> metadata:
> name: ealsticsearch
> 
> ```

s/ealsticsearch/elasticsearch ?

---

<div class="post-metadata">

### Author: ![expert1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/expert1/32/126753_2.png) [@expert1](https://discuss.elastic.co/u/expert1)
#### Post date: [October 24, 2023, 1:04am UTC](https://discuss.elastic.co/t/kibanas-is-stuck-after-elasticsearch-cluster-is-ready/345546/3 "2023-10-24T01:04:15Z")

</div>

oh, what a stupid mistake I have made. 🙂  
Thanks for pointing it out and it saves me my day.

---

<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: [November 21, 2023, 1:04am UTC](https://discuss.elastic.co/t/kibanas-is-stuck-after-elasticsearch-cluster-is-ready/345546/4 "2023-11-21T01:04:39Z")

</div>

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