kubernetes: node-local-dns fails in ipv6 only cluster

What happened: Deployment of node-local-dns in an ipv6-only cluster fails with the following iptables-related error

2020/07/30 13:49:00 [INFO] Using Corefile /etc/Corefile
2020/07/30 13:49:00 [INFO] Tearing down
2020/07/30 13:49:00 [INFO] Hit error during teardown - Link not found
2020/07/30 13:49:00 [INFO] Setting up networking for node cache
2020/07/30 13:49:00 [INFO] Tearing down
2020/07/30 13:49:00 [FATAL] Failed to setup - error checking rule: exit status 2: iptables v1.6.2: host/network `fd00:eca1:5000:aaaa::ffff:a' not found
Try `iptables -h' or 'iptables --help' for more information.
, Exiting

Does node-local-dns support binding to IPv6 addresses? If not, can node-local-dns be used in an ipv6-only cluster?

What you expected to happen: node-local-dns is up and running normally and binding to an ipv6 link-local address

How to reproduce it (as minimally and precisely as possible): Create an ipv6-only cluster using nodes with single ipv6 stack

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): v1.18.2
  • Cloud provider or hardware configuration: Openstack VMs
  • OS (e.g: cat /etc/os-release): SLES 15 SP1
  • Kernel (e.g. uname -a): 4.12.14-197.45-default
  • Install tools: kubeadm
  • Network plugin and version (if this is a network-related bug): calico v3.12.0
  • Others:

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 16 (12 by maintainers)

Most upvoted comments

Does node-local-dns support binding to IPv6 addresses? If not, can node-local-dns be used in an ipv6-only cluster?

Not yet, node-local-dns is not supported to run on ipv6-only clusters.