What line indicates that Filebeat 7.7.0 is creating an index in Elasticsearch. We are trying to debug the fact that its not creating an Elasticsearch index, but the harvester fails saying the index is missing. Isn't it the job of Filebeat to create this index when it starts, if so which lines in the logs
(obtained via kubectl logs <pod.id>) indicate that it is getting created in the first place.
Error log shows this
Could not init registrar: registry file version 1 not supported
Environment: Filebeat DaemonSet running in Kubernetes cluster