Skip to content

Health endpoint does not bind to tcp6 on a IPv6 only environment #13165

@lyind

Description

@lyind

Bug report

General Information

How to reproduce the issue

  1. Install K8s 1.19.1 using kubeadm with IPv6 only, skipping addon/kube-proxy
  2. Install cilium 1.8.3 using the attached config
  3. Monitor logs and READY state of "cilium" pod
  • issue: cilium never becomes READY, health endpoint restarting endlessly
  1. Create a pod like this and try to "ping6" your default gateway by IP (IPv6)
  • issue: connections or pings to nodes outside the cluster not possible, even if IP ranges are fully routable

Metadata

Metadata

Assignees

Labels

kind/bugThis is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.needs/triageThis issue requires triaging to establish severity and next steps.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions