Release note label not set, please set the appropriate release note.

Coverage increased (+0.007%) to 45.519% when pulling 968de865a7e87298df7e44cf3661a62bcc52d49f on ctripcloud:bird_guide into 43f7824 on cilium:master.

test-docs-please

Commit 9cd69cf215cf3a87e23a3d9696461bbeab3f63c1 does not contain "Signed-off-by".

Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/contributing/#developer-s-certificate-of-origin

Commits 9cd69cf215cf3a87e23a3d9696461bbeab3f63c1, 3e22ddc3ad742fe86566be4f19ccdd4b5a799b2a do not contain "Signed-off-by".

Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/contributing/#developer-s-certificate-of-origin

Commits 9cd69cf215cf3a87e23a3d9696461bbeab3f63c1, 3e22ddc3ad742fe86566be4f19ccdd4b5a799b2a, 5ae1bb146765074c247ddb5a3b6707d5325628dc, 45490bdea80e9e6c78c2d1ad169830a95e7dd5d8 do not contain "Signed-off-by".

Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/contributing/#developer-s-certificate-of-origin

hi @pchaigno , big thanks for your advises!

I have resolved them except two:

1. two pictures seems too large applying scale 70%
2. whether should i add sed commands to replace the placeholders in bird.conf

Commits 2899518813f2c09ed83c2b26044d9f8325eac295, 6f688cb145abdd9b239b0a9637edcadcbcdff26f, 4fdc010f06d3980563940a66edf16666750e3c6a do not contain "Signed-off-by".

Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/contributing/#developer-s-certificate-of-origin

Commits 2899518813f2c09ed83c2b26044d9f8325eac295, 6f688cb145abdd9b239b0a9637edcadcbcdff26f, 4fdc010f06d3980563940a66edf16666750e3c6a, 577200131e61f8b76e6281f5504e0a3ae7d06090, 87514dbfa03e7e8009c8047f8c828942c5f5935d do not contain "Signed-off-by".

Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/contributing/#developer-s-certificate-of-origin

Indeed i missed the hidden ones just now @pchaigno

test-docs-please

@ArthurChiao can this be backported to 1.7 as well, meaning, is it confirmed to work with 1.7 so it could go into the stable doc? Thx

@borkmann yes, i have tested Cilium 1.7.0 + bird 2.0.6 (but just tested one node), the scheme works ok.

Actually in my understanding, Cilium and bird works independently, they collaborate through kernel routing tables/facilities, so as long as they do not break their kernel conventions, each of them could be upgraded/downgraded transparently - or even, be replaced by their alternatives (that's how we rolling-replaced kube-router with bird).

@joestringer that's nice way for automation, but at present there are many challenges that may threaten the availability (both bird itself and the whole cluster) instead of strengthen it, such as:

1. bird daemon on each node has different configurations - with respect to your BGP peering scheme, these differences may include router ID, PodCIDR, peer ASN, peer IP, peer password, etc. I assume Daemonset is good at handling services with much the same configuration (e.g. via configmap)?
2. if Daemonset encountered some problems (e.g. problematic yaml), all bird daemons may exit and could not be re-launched, in this case, all announced routes will be withdrawn, then not only new Pods could not be deployed, but also all running Pods will be disconnected - the whole cluster suffers.

For these reason, we prefer standalone deployment of bird currently. However, i will consider your suggested way, thanks!