Filebeat add_kubernetes_metadata and IPv6


(Hart Hoover) #1

When using filebeat in a Kubernetes cluster as a pod, using the add_kubernetes_metadata processor, the processor can't handle IPv6 addresses if an IPv6 address resolves from https://kubernetes.default.svc.cluster.local. The parser freaks out on the colons in the address. I don't know if this is an issue in an underlying library or Filebeat itself.

Secondary to this issue, it would be nice to provide a custom Kubernetes API endpoint to use, so I could try something like https://[2001:0db8:85a3:0000:0000:8a2e:0370:7334]:443 (and force the use of brackets). It looks like I can only do this if I set in_cluster to "false" and provide a kubeconfig file.


(Pier-Hugues Pellerin) #2

Can you create a specific issue on our bug tracker at https://github.com/elastic/beats/,
When you say the parser freak out I presume it actually panic? Adding the trace to the issue would be really useful and we would be able to narrow it down to either beats or the library.


(Hart Hoover) #3

https://github.com/elastic/beats/issues/8749

Done, with the error included.


(Hart Hoover) #4

Is there any container pushed with the fix in it before 6.5's release that I can use in the meantime? I can even test it for you! :slight_smile:


(system) #5

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