Why can't logs go from pod to elasticsearch? Where can you dig?

Question

elasticsearch

kubectl logs  --namespace=xxx db-master-postgresql-59d9df468f-ksvth
LOG:  database system was interrupted; last known up at 2018-09-28 14:02:05 UTC
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  invalid record length at 0/1645768: wanted 24, got 0
LOG:  redo is not required
LOG:  MultiXact member wraparound protections are now enabled
LOG:  autovacuum launcher started
LOG:  database system is ready to accept connections

kubectl get pods --namespace=efk
NAME                          READY     STATUS    RESTARTS   AGE
efk-elasticsearch-0           1/1       Running   0          1h
efk-elasticsearch-1           1/1       Running   0          1h
efk-elasticsearch-2           1/1       Running   0          1h
efk-fluent-bit-58vn5          1/1       Running   0          1h
efk-fluent-bit-f9wl2          1/1       Running   0          1h
efk-fluent-bit-htk2w          1/1       Running   0          1h
efk-kibana-5775c58869-jspk9   1/1       Running   0          1h

those. according to this article https://logz.io/blog/kubernetes-log-analysis/
does fluentd mount /var/log/containers folder and send everything to Elasticsearch?

Answer 1

kubectl --namespace=efk exec -it efk-fluent-bit-58vn5 -- /bin/bash
[email protected]:/var/log/containers# ls | grep db-master
[email protected]:/var/log/containers#

went to fluentd - and there is no log there.