docs: add BFD support documentation for kube-ovn-speaker#408
Merged
Conversation
1 task
Contributor
Author
|
@oilbeater 大佬，这个 lint 和当前提交无关，不确定是否是 lint 执行相关的版本问题 |
zbb88888
force-pushed
the
kube-ovn-speaker-with-bfd
branch
5 times, most recently
from
0014766 to
f800f82
Compare
zbb88888
force-pushed
the
kube-ovn-speaker-with-bfd
branch
from
f800f82 to
556db67
Compare
Contributor
Author
|
@oilbeater hi, could you please help review? Thanks! |
oilbeater
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add BFD (Bidirectional Forwarding Detection) section to both Chinese and English BGP documentation, including:
BFD CLI flags in advanced options
Enabling BFD with configuration examples
Prerequisites (bidirectional requirement, firewall rules)
Verifying BFD status via gobgp JSON output
BFD failure behavior description
Make sure you have followed the Document Convention