I’m trying to create an ECK instance using the official documentation.
I’m a little bit confused as each time I try to create the Kibana instance I get the same error that the indexes already exist.
This being after a fresh install and non retained PVs.
I’ve additionally tried to delete the operator and re-apply it.
I had a working version but wanted to recreate with testing of the new “fleet” features (since I only have a basic license to play with, I assume the required xpack settings are not sufficient.)
apiVersion: elasticsearch.k8s.elastic.co/v1 kind: Elasticsearch metadata: name: elasticsearch namespace: elasticsearch spec: version: 7.9.3 nodeSets: - name: eck count: 1 config: node.master: true node.data: true node.ingest: true node.store.allow_mmap: false volumeClaimTemplates: - metadata: name: elasticsearch-data spec: storageClassName: rook-ceph-block accessModes: - ReadWriteOnce resources: requests: storage: 30Gi
apiVersion: kibana.k8s.elastic.co/v1 kind: Kibana metadata: name: elasticsearch namespace: elasticsearch spec: version: 7.9.3 count: 1 elasticsearchRef: name: elasticsearch
Logs from Kibana
”warning","savedobjects-service"],"pid":7,"message":"Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana_task_manager_1 and restarting Kibana."}