Skip to content

Bind fluent-bit listeners to the pod IP so IPv6 pods become Ready (EV-7169) - #5375

Closed
rene-dekker wants to merge 1 commit into
tigera:masterfrom
rene-dekker:EV-7169
Closed

rene-dekker wants to merge 1 commit into
tigera:masterfrom
rene-dekker:EV-7169

Conversation

@rene-dekker

Copy link
Copy Markdown
Member

Jira: https://tigera.atlassian.net/browse/EV-7169

fluent-bit's HTTP server (and the non-cluster-host in_http input) default to listening on 0.0.0.0. On an IPv6-only cluster the pod has no IPv4 address, so the kubelet's probes to [podIP]:2020 never connect: calico-fluent-bit stays 0/1, log-collector stays Degraded, and the weekly ce-ipv6 suite has never passed.

  • Bind http_listen and the in_http listen to ${POD_IP} (downward API status.podIP), for both the DaemonSet and the EKS log forwarder.
  • Pod IP rather than ::: works for v4, v6 and dual-stack, doesn't depend on IP pools (empty with non-Calico CNIs like AWS VPC CNI), and avoids :: failing on nodes with IPv6 disabled or being v6-only on Windows.
  • Rendered-config goldens regenerated.
Fixed calico-fluent-bit never becoming Ready on IPv6 clusters.

🤖 Generated with Claude Code

@rene-dekker

Copy link
Copy Markdown
Member Author

Wrong repo; operator code for master lives in calico-private.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants