Kibana not found in custom definitions using Istio

The deployment of the elastic operator is working fine, following the steps of this guide:
https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-service-mesh-istio.html

After deploying the Kibana, anything is starting. There is no Kibana pod launching and if we check the Kibana logs, we get the following message:

> kubectl logs kibana/kibana -n elastic-system
error: no kind "Kibana" is registered for version "kibana.k8s.elastic.co/v1" in the scheme "pkg/scheme/scheme.go:28"

I don't know why is happening when I installed all the custom resources definitions (kubectl create -f https://download.elastic.co/downloads/eck/2.6.1/crds.yaml)

Checking if I have the Kibana custom resource definition:

>kubectl get customresourcedefinitions
NAME                                                   CREATED AT
...
elasticmapsservers.maps.k8s.elastic.co                 2023-02-19T20:41:38Z
elasticsearchautoscalers.autoscaling.k8s.elastic.co    2023-02-19T20:53:41Z
elasticsearches.elasticsearch.k8s.elastic.co           2023-02-19T20:41:39Z
enterprisesearches.enterprisesearch.k8s.elastic.co     2023-02-19T20:41:39Z
envoyfilters.networking.istio.io                       2023-02-19T20:21:48Z
gateways.networking.istio.io                           2023-02-19T20:21:48Z
issuers.cert-manager.io                                2023-02-19T20:33:29Z
istiooperators.install.istio.io                        2023-02-19T20:21:48Z
kibanas.kibana.k8s.elastic.co                          2023-02-19T22:54:57Z
...
>kubectl get customresourcedefinitions/kibanas.kibana.k8s.elastic.co -o yaml
...
status:
  acceptedNames:
    categories:
    - elastic
    kind: Kibana
    listKind: KibanaList
    plural: kibanas
    shortNames:
    - kb
    singular: kibana
  conditions:
  - lastTransitionTime: "2023-02-19T22:54:57Z"
    message: no conflicts found
    reason: NoConflicts
    status: "True"
    type: NamesAccepted
  - lastTransitionTime: "2023-02-19T22:54:57Z"
    message: the initial names have been accepted
    reason: InitialNamesAccepted
    status: "True"
    type: Established
  storedVersions:
  - v1

So I don't know why the latest version of Kibana isn't working

Thank you so much in advance

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