Skip to content

Kibana status.version field not updated on upgrade #8838

@ailiev-ipq

Description

@ailiev-ipq

I have an ECK 3.1.0 running in a Kubernetes cluster and managing a single Elasticsearch/Kibana pair.

Initially Elasticsearch/Kibana were at version 8.13.2.

I updated the Elasticsearch/Kibana manifests, the only difference being the version bump from 8.13.2 to 8.19.3.

The Elasticsearch (three node cluster) was correctly upgraded to 8.19.3 and its version was correctly reported (e.g., in kubectl get elasticsearch).

During the Elasticsearch upgrade the Kibana resource got the following event in kubectl describe kibana:

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Warning  Delayed    13m (x2 over 13m)  kibana-controller  Delaying deployment of version 8.19.3 since the referenced elasticsearch is not upgraded yet

(which makes perfect sense.)

It looks like the Kibana was also upgraded after the Elasticsearch upgrade was complete, because:

  • I see in the Kibana UI that the version is 8.19.3 (and the UI differs from the 8.13.2 one)
  • the .spec.containers[0].image reports docker.elastic.co/kibana/kibana:8.19.3
    but kubectl get kibana still reports 8.13.2.

It seems that the upgrade had happened immediately after the Elasticsearch upgrade had finished (Elasticsearch phase Ready, health green), but this isn't reflected in the status.version field of the Kibana resource.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions