Why `elastic-es-default-0` (which is the pod name for my Elasticsearch) becomes a "host"?

It behaves like a host... For example, see the screenshot. The test-one-01106 is a real kubernetes worker machine, but the elastic-es-default-0 is not... Thanks!

I moved this question to the Security category because this screenshot looks like it was taken in the Security/SIEM app. I believe the question is why in a containerized deployment of the Elastic stack on k8s the Pod running the Elasticsearch process shows up as a host next to an actual physical host. But I don't know enough about how this app gets it's data to answer the question.

1 Like

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