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
fix(ipv6): follow the cluster families for the syslog-ng bind and the metrics bind
Three points from review.
The syslog-ng source bound "::" whenever enabledIPv6 was set. That reaches IPv4
clients only through v4-mapped addresses, which net.ipv6.bindv6only turns off.
On a node with that setting and a cluster without IPv6, the Service is IPv4 and
the source had no IPv4 listener, so ingestion failed. The bind now follows the
same cluster answer the Services use.
The buffer-metrics sidecars hard-coded their listen address, so a bind set on
bufferVolumeMetrics was accepted and dropped. They pass it through now. An unset
bind still yields the wildcard address.
A cluster with no IPv6 range is re-probed instead of cached, so a range added to
a running cluster is picked up without restarting the operator.
Signed-off-by: Bence Csati <bence.csati@axoflow.com>
0 commit comments