Describe the enhancement:
On some cases we need to correlate host names with kubernetes nodes, or filter events by kubernetes node using host names. On these cases we rely on host.name having a consistent value with kubernetes.node.name, but they are values of different nature:
host.name is the hostname as returned by the operating system.kubernetes.node.name is the node name as registered in the Kubernetes API, what could in theory be any string that matches as DNS subdomain.
Even if the kubernetes node name is most of the times the host name, we have seen cases where the OS reports the hostname as FQDN, and the kubernetes name is the same, but without the domain, what leads to host.name and kubernetes.node.name to have different values.
Kubernetes API reports more data about nodes apart of their name, including some hostnames. We could include the hostname in the events as a kubernetes.node.hostname field.
Hostnames can be found as addresses in node metadata, and the definition is coherent with the value used in Beats for host.name (The hostname as reported by the node’s kernel), see https://v1-17.docs.kubernetes.io/docs/concepts/architecture/nodes/#addresses
Describe a specific use case for the enhancement or feature:
Metrics UI shows nodes per host.name, but when zooming into kubernetes views it expects the kubernetes.node.name to be coherent with host.name so it can link from one view to the other and show the expected data.
Describe the enhancement:
On some cases we need to correlate host names with kubernetes nodes, or filter events by kubernetes node using host names. On these cases we rely on
host.namehaving a consistent value withkubernetes.node.name, but they are values of different nature:host.nameis the hostname as returned by the operating system.kubernetes.node.nameis the node name as registered in the Kubernetes API, what could in theory be any string that matches as DNS subdomain.Even if the kubernetes node name is most of the times the host name, we have seen cases where the OS reports the hostname as FQDN, and the kubernetes name is the same, but without the domain, what leads to
host.nameandkubernetes.node.nameto have different values.Kubernetes API reports more data about nodes apart of their name, including some hostnames. We could include the hostname in the events as a
kubernetes.node.hostnamefield.Hostnames can be found as addresses in node metadata, and the definition is coherent with the value used in Beats for
host.name(The hostname as reported by the node’s kernel), see https://v1-17.docs.kubernetes.io/docs/concepts/architecture/nodes/#addressesDescribe a specific use case for the enhancement or feature:
Metrics UI shows nodes per
host.name, but when zooming into kubernetes views it expects thekubernetes.node.nameto be coherent withhost.nameso it can link from one view to the other and show the expected data.