How to guarantee persistence of routes mananged by calico in kernel

[BlueBlue-Lee]

I have install calico with bgp mode in kubernetes and enable graceful restart capability on both calico and hardware switch side.

I want to know how to keep routes in kernel when calico-bird is stopped for short of time?

Expected Behavior

• routes managed by bird are keeped in kernel when calico-bird is restarted.
• routes advertised to peer switch are not withdrew and in stale state for some period

Current Behavior

• routes on local node are deleted
• routes on peer switch are not withdrew and in stale state for some period

I want to know is it in line with expectations? If not, how calico guarantee the persistence of kernel routing table when restart?

[caseydavenport]

Calico shouldn't be deleting local routes from the kernel when it restarts.

Could you provide the logs from the calico-node pod on the affected node? From both the shutdown and startup:

• shutdown: kubectl logs -p -n calico-system <podname>
• startup (after restart): kubectl logs -n calico-system <newpodname>