You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a dual-stack (or IPv6 only) cluster, localhost resolves to ::1. HAProxy is configured to log to localhost:514 and dutifully sends log messages to [::1]:514, but the whereisaaron/kube-syslog-sidecar listens only on the IPv4 0.0.0.0 address. Thus, the messages go nowhere:
A quick workaround for dual-stack clusters would be to change the localhost address to 127.0.0.1, but that wouldn't help IPv6-only clusters. Ideally the latter image would switch to using :: to listen, or have a configurable listen address.
Another potential workaround that I've just thought of is to use the "external" HAProxy, which can instead log to its own stdout. I'll give that a try and report back.
The text was updated successfully, but these errors were encountered:
Another potential workaround that I've just thought of is to use the "external" HAProxy, which can instead log to its own stdout. I'll give that a try and report back.
In a dual-stack (or IPv6 only) cluster,
localhost
resolves to::1
. HAProxy is configured to log tolocalhost:514
and dutifully sends log messages to[::1]:514
, but thewhereisaaron/kube-syslog-sidecar
listens only on the IPv40.0.0.0
address. Thus, the messages go nowhere:A quick workaround for dual-stack clusters would be to change the
localhost
address to127.0.0.1
, but that wouldn't help IPv6-only clusters. Ideally the latter image would switch to using::
to listen, or have a configurable listen address.Another potential workaround that I've just thought of is to use the "external" HAProxy, which can instead log to its own stdout. I'll give that a try and report back.
The text was updated successfully, but these errors were encountered: