Cloud Native应用交付

  • 首页
  • 关于本站
  • 个人介绍
  • Downloads
  • Repo
    • Github
    • Container
  • F5
    • F5 Python SDK
    • F5-container
    • F5-LBaaS
  • 社交
    • 联系我
    • 微信/微博
    • 公众号
    • 打赏赞助
行至水穷处 坐看云起时
Cloud Native Application Services: cnadn.net
  1. 首页
  2. F5技术
  3. 正文

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

2018年12月15日 7504点热度 0人点赞 0条评论
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:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
//k8s master//
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.10.201  netmask 255.255.0.0  broadcast 172.16.255.255
        inet6 fe80::93eb:77c9:718:43d2  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:b3:46:85  txqueuelen 1000  (Ethernet)
        RX packets 352566  bytes 32062651 (30.5 MiB)
        RX errors 0  dropped 4  overruns 0  frame 0
        TX packets 457619  bytes 416423360 (397.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.40.199  netmask 255.255.255.0  broadcast 172.16.40.255
        inet6 fe80::a35:8f62:68df:ae99  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:b3:09:f2  txqueuelen 1000  (Ethernet)
        RX packets 278  bytes 26665 (26.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 159  bytes 19746 (19.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1450
        inet 10.244.0.0  netmask 255.255.255.255  broadcast 0.0.0.0
        inet6 fe80::7046:9bff:fe13:8814  prefixlen 64  scopeid 0x20<link>
        ether 72:46:9b:13:88:14  txqueuelen 0  (Ethernet)
        RX packets 80  bytes 7731 (7.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 124  bytes 9276 (9.0 KiB)
        TX errors 0  dropped 8 overruns 0  carrier 0  collisions 0
 
//k8s master//
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.10.201  netmask 255.255.0.0  broadcast 172.16.255.255
        inet6 fe80::93eb:77c9:718:43d2  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:b3:46:85  txqueuelen 1000  (Ethernet)
        RX packets 352566  bytes 32062651 (30.5 MiB)
        RX errors 0  dropped 4  overruns 0  frame 0
        TX packets 457619  bytes 416423360 (397.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.40.199  netmask 255.255.255.0  broadcast 172.16.40.255
        inet6 fe80::a35:8f62:68df:ae99  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:b3:09:f2  txqueuelen 1000  (Ethernet)
        RX packets 278  bytes 26665 (26.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 159  bytes 19746 (19.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1450
        inet 10.244.0.0  netmask 255.255.255.255  broadcast 0.0.0.0
        inet6 fe80::7046:9bff:fe13:8814  prefixlen 64  scopeid 0x20<link>
        ether 72:46:9b:13:88:14  txqueuelen 0  (Ethernet)
        RX packets 80  bytes 7731 (7.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 124  bytes 9276 (9.0 KiB)
        TX errors 0  dropped 8 overruns 0  carrier 0  collisions 0
 
[root@k8s-master f5-k8s]# bridge fdb
00:50:56:b3:2e:29 dev flannel.1 dst 172.16.40.202 self permanent
72:45:92:84:7e:ac dev flannel.1 dst 172.16.40.198 self permanent
 
 
 
 
//k8s-node1//
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.10.202  netmask 255.255.255.0  broadcast 172.16.10.255
        inet6 fe80::2cb4:4e38:b3cc:e972  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:b3:0c:71  txqueuelen 1000  (Ethernet)
        RX packets 457633  bytes 311060432 (296.6 MiB)
        RX errors 0  dropped 5  overruns 0  frame 0
        TX packets 352387  bytes 32126104 (30.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.40.198  netmask 255.255.255.0  broadcast 172.16.40.255
        inet6 fe80::53f1:b4f9:30d7:7da2  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:b3:1b:9b  txqueuelen 1000  (Ethernet)
        RX packets 145668  bytes 141254015 (134.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 139284  bytes 51315882 (48.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1450
        inet 10.244.1.0  netmask 255.255.255.255  broadcast 0.0.0.0
        inet6 fe80::7045:92ff:fe84:7eac  prefixlen 64  scopeid 0x20<link>
        ether 72:45:92:84:7e:ac  txqueuelen 0  (Ethernet)
        RX packets 96  bytes 6924 (6.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 80  bytes 7731 (7.5 KiB)
        TX errors 0  dropped 8 overruns 0  carrier 0  collisions 0
 
 
[root@k8s-node1 ~]# bridge fdb
00:50:56:b3:2e:29 dev flannel.1 dst 172.16.40.202 self permanent
72:46:9b:13:88:14 dev flannel.1 dst 172.16.40.199 self permanent
da:05:79:a8:36:93 dev flannel.1 dst 172.16.40.199 self permanent

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

1
2
[root@k8s-node1 ~]# curl 10.250.0.75
This is k8s-node1 /root/cka/data/index.html
  • Set F5 as a fake node for k8s, and set vxlan, here is BIGIP setting:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
myf5@(v13-common)(cfg-sync Not All Devices Synced)(Active)(/Common)(tmos)# list net self
net self self_flannel_vxlan { <<<<<<<<<<<<<<<<<<<<<
    address 10.244.244.2/16
    allow-service {
        default
    }
    traffic-group traffic-group-local-only
    vlan flannel_tunel_vxlan
}
net self ext_self_v6 {
    address fdf1:f2f3:f4f5:f6f7::ac10:1eca/64
    allow-service {
        default
    }
    traffic-group traffic-group-local-only
    vlan ext_vlan
}
net self ext_self {
    address 172.16.30.202/24
    allow-service {
        default
    }
    traffic-group traffic-group-local-only
    vlan ext_vlan
}
net self float_self_flannel_vxlan { <<<<<<<<<<<<<<<<<
    address 10.244.244.3/16
    allow-service {
        default
    }
    floating enabled
    traffic-group traffic-group-1
    unit 1
    vlan flannel_tunel_vxlan
}
net self vtep {   <<<<<<<<<<<<<<<<<<<
    address 172.16.40.202/24
    allow-service {
        default
    }
    traffic-group traffic-group-local-only
    vlan int_vlan
}
 
 
myf5@(v13-common)(cfg-sync Not All Devices Synced)(Active)(/Common)(tmos)# list net tunnels vxlan
net tunnels vxlan fl-vxlan {
    app-service none
    flooding-type none
    port otv
}
 
 
myf5@(v13-common)(cfg-sync Not All Devices Synced)(Active)(/Common)(tmos)# list net tunnels tunnel flannel_tunel_vxlan
net tunnels tunnel flannel_tunel_vxlan {
    if-index 208
    key 1
    local-address 172.16.40.202
    profile fl-vxlan
}

The bigip is using node internal IP for FDB:

1
2
3
4
5
6
7
8
myf5@(v13-common)(cfg-sync Not All Devices Synced)(Active)(/Common)(tmos)# show net fdb
 
-------------------------------------------------------------------------
Net::FDB          
Tunnel               Mac Address        Member                    Dynamic
-------------------------------------------------------------------------
flannel_tunel_vxlan  72:46:9b:13:88:14  endpoint:172.16.10.201%0  no
flannel_tunel_vxlan  72:45:92:84:7e:ac  endpoint:172.16.10.202%0  no

And arp can not be set:

1
2
3
4
5
6
7
8
9
myf5@(v13-common)(cfg-sync Not All Devices Synced)(Active)(/Common)(tmos)# show net arp
 
-----------------------------------------------------------------------------------------------------
Net::Arp    
Name           Address        HWaddress          Vlan                         Expire-in-sec  Status
-----------------------------------------------------------------------------------------------------
10.244.1.4     10.244.1.4     incomplete         /Common/flannel_tunel_vxlan  0              unknown <<<<<!!!
172.16.30.203  172.16.30.203  00:50:56:b3:03:ff  /Common/ext_vlan             294            resolved
172.16.40.198  172.16.40.198  00:50:56:b3:1b:9b  /Common/int_vlan             254            resolved

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

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
[root@k8s-node1 ~]# kubectl get nodes -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: Node
  metadata:
    annotations:
      flannel.alpha.coreos.com/backend-data: '{"VtepMAC":"00:50:56:b3:2e:29"}'
      flannel.alpha.coreos.com/backend-type: vxlan
      flannel.alpha.coreos.com/kube-subnet-manager: "true"
      flannel.alpha.coreos.com/public-ip: 172.16.40.202
      node.alpha.kubernetes.io/ttl: "0"
    creationTimestamp: 2018-12-14T15:17:46Z
    name: bigip
    namespace: ""
    resourceVersion: "7342120"
    selfLink: /api/v1/nodes/bigip
    uid: 6933c860-ffb3-11e8-9344-005056b34685
  spec:
    externalID: bigip
    podCIDR: 10.244.244.0/24
  status:
    conditions:
    - lastHeartbeatTime: 2018-12-14T15:17:46Z
      lastTransitionTime: 2018-12-14T15:18:47Z
      message: Kubelet never posted node status.
      reason: NodeStatusNeverUpdated
      status: Unknown
      type: Ready
    - lastHeartbeatTime: 2018-12-14T15:17:46Z
      lastTransitionTime: 2018-12-14T15:18:47Z
      message: Kubelet never posted node status.
      reason: NodeStatusNeverUpdated
      status: Unknown
      type: OutOfDisk
    - lastHeartbeatTime: 2018-12-14T15:17:46Z
      lastTransitionTime: 2018-12-14T15:18:47Z
      message: Kubelet never posted node status.
      reason: NodeStatusNeverUpdated
      status: Unknown
      type: MemoryPressure
    - lastHeartbeatTime: 2018-12-14T15:17:46Z
      lastTransitionTime: 2018-12-14T15:18:47Z
      message: Kubelet never posted node status.
      reason: NodeStatusNeverUpdated
      status: Unknown
      type: DiskPressure
    daemonEndpoints:
      kubeletEndpoint:
        Port: 0
    nodeInfo:
      architecture: ""
      bootID: ""
      containerRuntimeVersion: ""
      kernelVersion: ""
      kubeProxyVersion: ""
      kubeletVersion: ""
      machineID: ""
      operatingSystem: ""
      osImage: ""
      systemUUID: ""
- apiVersion: v1
  kind: Node
  metadata:
    annotations:
      flannel.alpha.coreos.com/backend-data: '{"VtepMAC":"72:46:9b:13:88:14"}'
      flannel.alpha.coreos.com/backend-type: vxlan
      flannel.alpha.coreos.com/kube-subnet-manager: "true"
      flannel.alpha.coreos.com/public-ip: 172.16.40.199
      node.alpha.kubernetes.io/ttl: "0"
      volumes.kubernetes.io/controller-managed-attach-detach: "true"
    creationTimestamp: 2018-08-05T14:42:30Z
    labels:
      beta.kubernetes.io/arch: amd64
      beta.kubernetes.io/os: linux
      kubernetes.io/hostname: k8s-master
      owner: lj
      role: master
    name: k8s-master
    namespace: ""
    resourceVersion: "7439863"
    selfLink: /api/v1/nodes/k8s-master
    uid: c7b4efba-98bd-11e8-aeed-000c29850765
  spec:
    externalID: k8s-master
    podCIDR: 10.244.0.0/24
  status:
    addresses:
    - address: 172.16.10.201
      type: InternalIP
    - address: k8s-master
      type: Hostname
    allocatable:
      cpu: "1"
      ephemeral-storage: 17868Mi
      hugepages-1Gi: "0"
      hugepages-2Mi: "0"
      memory: 8152044Ki
      pods: "110"
    capacity:
      cpu: "1"
      ephemeral-storage: 17878Mi
      hugepages-1Gi: "0"
      hugepages-2Mi: "0"
      memory: 8157164Ki
      pods: "110"
    conditions:
    - lastHeartbeatTime: 2018-12-15T13:44:48Z
      lastTransitionTime: 2018-10-17T00:00:34Z
      message: kubelet has sufficient disk space available
      reason: KubeletHasSufficientDisk
      status: "False"
      type: OutOfDisk
    - lastHeartbeatTime: 2018-12-15T13:44:48Z
      lastTransitionTime: 2018-10-17T00:00:35Z
      message: kubelet has sufficient memory available
      reason: KubeletHasSufficientMemory
      status: "False"
      type: MemoryPressure
    - lastHeartbeatTime: 2018-12-15T13:44:48Z
      lastTransitionTime: 2018-11-27T06:21:00Z
      message: kubelet has no disk pressure
      reason: KubeletHasNoDiskPressure
      status: "False"
      type: DiskPressure
    - lastHeartbeatTime: 2018-12-15T13:44:48Z
      lastTransitionTime: 2018-08-05T14:42:30Z
      message: kubelet has sufficient PID available
      reason: KubeletHasSufficientPID
      status: "False"
      type: PIDPressure
    - lastHeartbeatTime: 2018-12-15T13:44:48Z
      lastTransitionTime: 2018-12-14T07:41:00Z
      message: kubelet is posting ready status
      reason: KubeletReady
      status: "True"
      type: Ready
    daemonEndpoints:
      kubeletEndpoint:
        Port: 10250
    images:
    - names:
      - f5devcentral/f5-as3-container@sha256:bb5aa050ba3839249038b579552b931f1e7ecea4ef177cf4c804779879625508
      - f5devcentral/f5-as3-container:latest
      sizeBytes: 487911870
    - names:
      - cargo.caicloud.io/caicloud/training-calico-node@sha256:2d5255fab62c29226a9a4121e1251439c2861641532edd653a009c11f4ec1b4f
      - cargo.caicloud.io/caicloud/training-calico-node:v2.6.2
      sizeBytes: 281619208
    - names:
      - f5networks/k8s-bigip-ctlr@sha256:120f45d5c8f57397d9ea95fa060361c46c1cb1a18d80f3c5d110d1d0b85652d5
      - f5networks/k8s-bigip-ctlr:latest
      sizeBytes: 266809874
    - names:
      - nginx@sha256:59f8d756e723a610d60bdcb37a4d68185a7b67bfc7ef4c616dd022458ec3db3a
      - nginx@sha256:5d32f60db294b5deb55d078cd4feb410ad88e6fe77500c87d3970eca97f54dba
      - nginx:latest
      sizeBytes: 109096776
    - names:
      - myf5/kubernetes-dashboard-amd64@sha256:2d41043bb04f32d2349ace6851fb80c50c689e38a94df1bfcb80802ccbbe09fd
      - myf5/kubernetes-dashboard-amd64:v1.8.3
      sizeBytes: 102319441
    - names:
      - cargo.caicloud.io/caicloud/training-calico-cni@sha256:063dafaee87aa7882fda7844de9258cd17666b3d61ce4547c910fca0326f0708
      - cargo.caicloud.io/caicloud/training-calico-cni:v1.11.0
      sizeBytes: 70883432
    - names:
      - cargo.caicloud.io/caicloud/training-flannel@sha256:93952a105b4576e8f09ab8c4e00483131b862c24180b0b7d342fb360bbe44f3d
      - cargo.caicloud.io/caicloud/training-flannel:v0.9.1
      sizeBytes: 51314612
    - names:
      - cargo.caicloud.io/caicloud/training-k8s-dns-kube-dns-amd64@sha256:5e69a3242bfb784dd3d678aa55675144f6780ebfc9c12a04f2fcaefe1f57eb7d
      - cargo.caicloud.io/caicloud/training-k8s-dns-kube-dns-amd64:1.14.4
      sizeBytes: 49383112
    - names:
      - cargo.caicloud.io/caicloud/training-k8s-dns-sidecar-amd64@sha256:dfaa92808121abce0a45da739179db653b230171cad4d582cf152967c07a68d3
      - cargo.caicloud.io/caicloud/training-k8s-dns-sidecar-amd64:1.14.4
      sizeBytes: 41814878
    - names:
      - cargo.caicloud.io/caicloud/training-k8s-dns-dnsmasq-nanny-amd64@sha256:f403d0b737d7229349ccf638dbc3c538b326048970f679738c27ca0bbcf859df
      - cargo.caicloud.io/caicloud/training-k8s-dns-dnsmasq-nanny-amd64:1.14.4
      sizeBytes: 41410758
    - names:
      - nginx@sha256:1134289c4e177da4547cfa9a97e41943cf03c29520f084d1c4e4622474c8e0e9
      - nginx:1.15-alpine
      sizeBytes: 17750118
    - names:
      - nginx@sha256:94e890939a012d8494ac62a0cf6177c57f97522b35e231dad676e089e309d49d
      sizeBytes: 17745892
    - names:
      - cargo.caicloud.io/caicloud/busybox@sha256:956f6d761c249b42459915ea9a094b84b82f3cdf815f11dd9c91fc5c23f0647a
      - cargo.caicloud.io/caicloud/busybox:1.24
      sizeBytes: 1113554
    - names:
      - cargo.caicloud.io/caicloud/pause-amd64@sha256:eb7d5e4b850dae2cd24897b8a74336459f6eb321e2538d33902f9919eb4f4c98
      - cargo.caicloud.io/caicloud/pause-amd64:3.0
      sizeBytes: 746888
    nodeInfo:
      architecture: amd64
      bootID: 8a175893-cc0b-4204-b156-b8cd4f7ea20d
      containerRuntimeVersion: docker://18.6.0
      kernelVersion: 3.10.0-862.9.1.el7.x86_64
      kubeProxyVersion: v1.10.6
      kubeletVersion: v1.10.6
      machineID: 0edb716e1cf347faa490b2a81c5e6dcd
      operatingSystem: linux
      osImage: CentOS Linux 7 (Core)
      systemUUID: 86FF3342-51DF-DCD5-A390-33A8B53D04A9
- apiVersion: v1
  kind: Node
  metadata:
    annotations:
      flannel.alpha.coreos.com/backend-data: '{"VtepMAC":"72:45:92:84:7e:ac"}'
      flannel.alpha.coreos.com/backend-type: vxlan
      flannel.alpha.coreos.com/kube-subnet-manager: "true"
      flannel.alpha.coreos.com/public-ip: 172.16.40.198
      node.alpha.kubernetes.io/ttl: "0"
      volumes.kubernetes.io/controller-managed-attach-detach: "true"
    creationTimestamp: 2018-08-05T17:10:45Z
    labels:
      beta.kubernetes.io/arch: amd64
      beta.kubernetes.io/os: linux
      kubernetes.io/hostname: k8s-node1
      owner: lj
      role: node
    name: k8s-node1
    namespace: ""
    resourceVersion: "7439862"
    selfLink: /api/v1/nodes/k8s-node1
    uid: 7dff767b-98d2-11e8-aeed-000c29850765
  spec:
    externalID: k8s-node1
    podCIDR: 10.244.1.0/24
  status:
    addresses:
    - address: 172.16.10.202
      type: InternalIP
    - address: k8s-node1
      type: Hostname
    allocatable:
      cpu: "1"
      ephemeral-storage: 17868Mi
      hugepages-1Gi: "0"
      hugepages-2Mi: "0"
      memory: 8152052Ki
      pods: "110"
    capacity:
      cpu: "1"
      ephemeral-storage: 17878Mi
      hugepages-1Gi: "0"
      hugepages-2Mi: "0"
      memory: 8157172Ki
      pods: "110"
    conditions:
    - lastHeartbeatTime: 2018-12-15T13:44:48Z
      lastTransitionTime: 2018-11-25T07:48:12Z
      message: kubelet has sufficient disk space available
      reason: KubeletHasSufficientDisk
      status: "False"
      type: OutOfDisk
    - lastHeartbeatTime: 2018-12-15T13:44:48Z
      lastTransitionTime: 2018-11-25T07:48:12Z
      message: kubelet has sufficient memory available
      reason: KubeletHasSufficientMemory
      status: "False"
      type: MemoryPressure
    - lastHeartbeatTime: 2018-12-15T13:44:48Z
      lastTransitionTime: 2018-11-27T07:03:34Z
      message: kubelet has no disk pressure
      reason: KubeletHasNoDiskPressure
      status: "False"
      type: DiskPressure
    - lastHeartbeatTime: 2018-12-15T13:44:48Z
      lastTransitionTime: 2018-08-06T01:41:16Z
      message: kubelet has sufficient PID available
      reason: KubeletHasSufficientPID
      status: "False"
      type: PIDPressure
    - lastHeartbeatTime: 2018-12-15T13:44:48Z
      lastTransitionTime: 2018-11-28T00:34:13Z
      message: kubelet is posting ready status
      reason: KubeletReady
      status: "True"
      type: Ready
    daemonEndpoints:
      kubeletEndpoint:
        Port: 10250
    images:
    - names:
      - f5devcentral/f5-as3-container@sha256:9ccf5a8e18699742440ea50b9023a9728987d04da4710869e8964d36bcf1d552
      - f5devcentral/f5-as3-container:3.5.0
      sizeBytes: 485211181
    - names:
      - cargo.caicloud.io/caicloud/training-calico-node@sha256:2d5255fab62c29226a9a4121e1251439c2861641532edd653a009c11f4ec1b4f
      - cargo.caicloud.io/caicloud/training-calico-node:v2.6.2
      sizeBytes: 281619208
    - names:
      - f5networks/k8s-bigip-ctlr@sha256:32e391b85b1cd100fd4d0e471e8fda0c02397089710db1bba8140337ed3ddbda
      - f5networks/k8s-bigip-ctlr:latest
      sizeBytes: 272118575
    - names:
      - nginx@sha256:5d32f60db294b5deb55d078cd4feb410ad88e6fe77500c87d3970eca97f54dba
      - nginx:latest
      sizeBytes: 109096776
    - names:
      - cargo.caicloud.io/caicloud/training-calico-cni@sha256:063dafaee87aa7882fda7844de9258cd17666b3d61ce4547c910fca0326f0708
      - cargo.caicloud.io/caicloud/training-calico-cni:v1.11.0
      sizeBytes: 70883432
    - names:
      - cargo.caicloud.io/caicloud/training-flannel@sha256:93952a105b4576e8f09ab8c4e00483131b862c24180b0b7d342fb360bbe44f3d
      - cargo.caicloud.io/caicloud/training-flannel:v0.9.1
      sizeBytes: 51314612
    - names:
      - busybox@sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812
      - busybox:latest
      sizeBytes: 1154353
    - names:
      - cargo.caicloud.io/caicloud/pause-amd64@sha256:eb7d5e4b850dae2cd24897b8a74336459f6eb321e2538d33902f9919eb4f4c98
      - cargo.caicloud.io/caicloud/pause-amd64:3.0
      sizeBytes: 746888
    nodeInfo:
      architecture: amd64
      bootID: 6695510b-6607-45d9-b300-1e17c14e4f19
      containerRuntimeVersion: docker://18.6.0
      kernelVersion: 3.10.0-862.9.1.el7.x86_64
      kubeProxyVersion: v1.10.6
      kubeletVersion: v1.10.6
      machineID: 0edb716e1cf347faa490b2a81c5e6dcd
      operatingSystem: linux
      osImage: CentOS Linux 7 (Core)
      systemUUID: 6D0B3342-1F42-BC9A-0FFE-BC296CF29F6F
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

上述问题是因为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

相关文章

  • Prometheus metrics of F5 CIS/CC
  • F5-k8s解决方案(2)-基于Calico BGP网络的F5 k8s容器平台方案实践
  • F5 CC 租户配置隔离配置方法
  • F5 k8s解决方案(1)- 基于 flannel vxlan模型的K8S解决方案
  • 项目:k8s Gateway API 的BIG-IP实现
本作品采用 知识共享署名-非商业性使用 4.0 国际许可协议 进行许可
标签: bigip cc k8s
最后更新:2018年12月29日

纳米

linjing.io

打赏 点赞
< 上一篇
下一篇 >

文章评论

razz evil exclaim smile redface biggrin eek confused idea lol mad twisted rolleyes wink cool arrow neutral cry mrgreen drooling persevering
取消回复

这个站点使用 Akismet 来减少垃圾评论。了解你的评论数据如何被处理。

页面AI聊天助手

纳米

linjing.io

☁️迈向Cloud Native ADC ☁️

认证获得:
TOGAF: ID 152743
Kubernetes: CKA #664
Microsoft: MCSE MCDBA
Cisco: CCNP
Juniper: JNCIS
F5:
F5 Certified Solution Expert, Security
F5 Certified Technology Specialist, LTM/GTM/APM/ASM
F5 Certified BIG-IP Administrator
  • 点击查看本博技术要素列表
  • 归档
    分类
    • AI
    • Automation
    • Avi Networks
    • Cisco ACI
    • CISCO资源
    • F5 with ELK
    • F5-Tech tips
    • F5技术
    • Juniper
    • Linux
    • NGINX
    • SDN
    • ServiceMesh
    • WEB编程
    • WINDOWS相关
    • 业界文章
    • 交换机技术
    • 化云为雨/Openstack
    • 协议原理
    • 容器/k8s
    • 我的工作
    • 我的生活
    • 网站技术
    • 路由器技术
    • 项目案例
    标签聚合
    neutron bigip flannel nginx api docker gtm openstack network DNS envoy irule istio k8s F5
    最近评论
    汤姆 发布于 8 个月前(09月10日) 嗨,楼主,里面的json怎么下载啊,怎么收费啊?
    汤姆 发布于 8 个月前(09月09日) 大佬,kib的页面可以分享下吗?谢谢
    zhangsha 发布于 1 年前(05月12日) 资料发给我下,谢谢纳米同志!!!!lyx895@qq.com
    李成才 发布于 1 年前(01月02日) 麻烦了,谢谢大佬
    纳米 发布于 1 年前(01月02日) 你好。是的,因为以前下载系统插件在一次升级后将所有的下载生成信息全弄丢了。所以不少文件无法下载。DN...
    浏览次数
    • Downloads - 183,756 views
    • 联系我 - 118,966 views
    • 迄今为止最全最深入的BIGIP-DNS/GTM原理及培训资料 - 116,489 views
    • Github - 103,645 views
    • F5常见log日志解释 - 79,768 views
    • 从传统ADC迈向CLOUD NATIVE ADC - 下载 - 74,619 views
    • Sniffer Pro 4 70 530抓包软件 中文版+视频教程 - 74,320 views
    • 迄今为止最全最深入的BIGIP-DNS/GTM原理及培训资料 - 67,770 views
    • 关于本站 - 60,890 views
    • 这篇文档您是否感兴趣 - 55,491 views
    链接表
    • F5SE创新
    • Jimmy Song‘s Blog
    • SDNlab
    • Service Mesh社区
    • 三斗室
    • 个人profile
    • 云原生社区

    COPYRIGHT © 2023 Cloud Native 应用交付. ALL RIGHTS RESERVED.

    Theme Kratos Made By Seaton Jiang

    京ICP备14048088号-1

    京公网安备 11010502041506号