行至水穷处 坐看“云”起时

Cloud Native ADN -> CNadn.Net

[issue-Fixed]多网络平面下bigip cc使用node internal ip导致FDB表插入错误

Description

Here is my k8s cluster environment:

  1. Set k8s cluster uses ens33 (172.16.10.0/24) for k8s cluster everything(certificates, Node internalIP, /etc/hosts setting)
  2. Set flannel to use ens160, for vxlan, so flannel public-ip is using 172.16.40.0/24 net. This is different to the node internal IP net.

Nodes interfaces:

Everything is ok, like: curl k8s-svc-luster-ip in the node self.

  • Set F5 as a fake node for k8s, and set vxlan, here is BIGIP setting:

The bigip is using node internal IP for FDB:

And arp can not be set:

The bigip-ctrl logs shows:
2018/12/15 01:19:27 [ERROR] Vxlan manager could not get VtepMac for 10.244.0.59’s node.

After checking the vxlan mgmr source code, The above logs was caused different node internal ip and flannel public-ip.

From the source code, also can find the bigip-ctrl is using node internal IP for fdb records.

Should the bigip-ctrl use flannel public-ip for node vtep here?

Kubernetes Version

Controller Version

Version: v1.7.1, BuildInfo: n1279-465125010

BIG-IP Version

Product BIG-IP
Version 13.1.1
Build 0.0.4
Edition Final
Date Fri Jul 20 17:55:49 PDT 2018

Diagnostic Information

上述问题是因为cc只能使用k8s的管理平面网络作为vxlan网络,而flannel是容许设置独立的网卡作为vxlan网络,这导致在k8s管理网络与容器vxlan网络流量分离的场景下cc无法正常工作。

该问题已被解决,使用镜像 myf5/k8s-bigip-ctlr:1.7.1 即可

问题详细见:

github issues见https://github.com/F5Networks/k8s-bigip-ctlr/issues/797

点赞

发表评论

电子邮件地址不会被公开。 必填项已用*标注