Skip to content

docs: add Kube-OVN BGP configuration guide#673

Merged
oilbeater merged 1 commit intomasterfrom
bgp-support
Apr 17, 2026
Merged

docs: add Kube-OVN BGP configuration guide#673
oilbeater merged 1 commit intomasterfrom
bgp-support

Conversation

@oilbeater
Copy link
Copy Markdown
Member

@oilbeater oilbeater commented Apr 17, 2026

Summary

This change adds an English guide for configuring BGP with Kube-OVN (configure_bgp.mdx), adapted from the upstream Kube-OVN BGP documentation. Sections for advertising ClusterIP Services and EIPs are intentionally omitted. The BGP route debugging section is not included.

Changes

  • New docs/en/configure/networking/how_to/kube_ovn/configure_bgp.mdx: kube-ovn-speaker installation, Pod/Subnet route advertisement, Cluster vs Local announcement policies, and advanced BGP options.
  • understanding_kube_ovn.mdx: link the kube-ovn-speaker subsection to the new page.

Notes

Navigation picks up the new page via the existing Kube OVN <Overview /> index; no doom.config.yml export changes are required.

Add configure_bgp.mdx covering kube-ovn-speaker installation, Pod and
Subnet route advertisement, announcement policies, and debugging.

Content is adapted from upstream Kube-OVN BGP documentation with
Service and EIP sections omitted. Link the kube-ovn-speaker overview
to the new page.

Made-with: Cursor
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 17, 2026

Walkthrough

A new comprehensive BGP configuration guide was added to the Kube-OVN documentation, covering how to set up kube-ovn-speaker, configure GoBGP parameters, and manage route advertisement policies. An existing Kube-OVN documentation page was updated to reference this new guide.

Changes

Cohort / File(s) Summary
BGP Configuration Documentation
docs/en/configure/networking/how_to/kube_ovn/configure_bgp.mdx, docs/en/configure/networking/how_to/kube_ovn/understanding_kube_ovn.mdx
Added detailed BGP route advertisement guide covering node labeling, speaker deployment, GoBGP configuration, annotation-based policies (Cluster and Local), and subnet settings. Updated existing documentation with reference link to new guide.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~8 minutes

Poem

🐰 With whiskers twitching, I hop through the docs so new,
BGP speakers announce routes, both silver and blue,
Annotations and policies, Cluster and Local too,
The network now gossips of paths fair and true! 🌐✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'docs: add Kube-OVN BGP configuration guide' directly and clearly summarizes the main change: adding new documentation for Kube-OVN BGP configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch bgp-support

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
docs/en/configure/networking/how_to/kube_ovn/understanding_kube_ovn.mdx (1)

95-96: Polish wording for readability.

Current phrasing is grammatically awkward (“a specific labeled nodes”, “to the external”). A small rewrite will read cleaner.

Proposed wording
-This component is a DaemonSet running on a specific labeled nodes that publish routes to the external,
-allowing external access to the container directly through the Pod IP. For deployment and BGP options, see [Configure BGP](./configure_bgp.mdx).
+This component is a DaemonSet running on specifically labeled nodes that publish routes to external networks,
+allowing direct external access to containers via Pod IPs. For deployment and BGP options, see [Configure BGP](./configure_bgp.mdx).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/en/configure/networking/how_to/kube_ovn/understanding_kube_ovn.mdx`
around lines 95 - 96, The sentence "This component is a DaemonSet running on a
specific labeled nodes that publish routes to the external, allowing external
access to the container directly through the Pod IP." is awkwardly phrased;
replace it with a clearer sentence such as: "This component is a DaemonSet
running on specifically labeled nodes that advertise routes to external
networks, allowing external access to containers directly via their Pod IPs."
Keep the trailing reference unchanged: "For deployment and BGP options, see
[Configure BGP](./configure_bgp.mdx)."
docs/en/configure/networking/how_to/kube_ovn/configure_bgp.mdx (1)

93-94: Unify annotation value examples for clarity.

Earlier examples use ovn.kubernetes.io/bgp=true, while this section highlights ...=yes. Please list both explicitly (or standardize on one) to avoid ambiguity.

Proposed wording tweak
-- `ovn.kubernetes.io/bgp=cluster`, or the default `ovn.kubernetes.io/bgp=yes`, selects the **Cluster** policy.
+- `ovn.kubernetes.io/bgp=cluster`, or boolean-style values such as `ovn.kubernetes.io/bgp=true` / `ovn.kubernetes.io/bgp=yes`, select the **Cluster** policy.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/en/configure/networking/how_to/kube_ovn/configure_bgp.mdx` around lines
93 - 94, The annotation examples for ovn.kubernetes.io/bgp are inconsistent
(this section shows `...=yes` while earlier examples use `...=true`); update the
two lines for clarity so they either list both equivalent values or standardize
to one. Specifically, change the Cluster-policy line to show both variants like
`ovn.kubernetes.io/bgp=cluster` (or `ovn.kubernetes.io/bgp=true/yes`) and the
Local-policy line to show `ovn.kubernetes.io/bgp=local` (or indicate `true/yes`
is equivalent where applicable), ensuring the annotation key
ovn.kubernetes.io/bgp and the values cluster, local, yes, true are explicitly
referenced.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/en/configure/networking/how_to/kube_ovn/configure_bgp.mdx`:
- Around line 96-106: Add a missing "Verify/Debug with gobgp" section after the
BGP advanced options that outlines common checks and example gobgp commands to
validate peering and routes; specifically mention verifying neighbor state with
gobgp neighbor, checking global and local RIB with gobgp global and gobgp rib
(or gobgp table), using gobgp monitor for live updates, and troubleshooting tips
(verify session TCP connectivity, auth/password mismatch, MTU/ebgp-multihop, and
holdtime/graceful-restart settings). Keep the guidance concise, include sample
command usages and expected outcomes, and reference the section title
"Verify/Debug with gobgp" so reviewers can find it easily.

---

Nitpick comments:
In `@docs/en/configure/networking/how_to/kube_ovn/configure_bgp.mdx`:
- Around line 93-94: The annotation examples for ovn.kubernetes.io/bgp are
inconsistent (this section shows `...=yes` while earlier examples use
`...=true`); update the two lines for clarity so they either list both
equivalent values or standardize to one. Specifically, change the Cluster-policy
line to show both variants like `ovn.kubernetes.io/bgp=cluster` (or
`ovn.kubernetes.io/bgp=true/yes`) and the Local-policy line to show
`ovn.kubernetes.io/bgp=local` (or indicate `true/yes` is equivalent where
applicable), ensuring the annotation key ovn.kubernetes.io/bgp and the values
cluster, local, yes, true are explicitly referenced.

In `@docs/en/configure/networking/how_to/kube_ovn/understanding_kube_ovn.mdx`:
- Around line 95-96: The sentence "This component is a DaemonSet running on a
specific labeled nodes that publish routes to the external, allowing external
access to the container directly through the Pod IP." is awkwardly phrased;
replace it with a clearer sentence such as: "This component is a DaemonSet
running on specifically labeled nodes that advertise routes to external
networks, allowing external access to containers directly via their Pod IPs."
Keep the trailing reference unchanged: "For deployment and BGP options, see
[Configure BGP](./configure_bgp.mdx)."
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fc7096c4-a915-4490-9096-712e12c0b641

📥 Commits

Reviewing files that changed from the base of the PR and between 0f11983 and 5f86e6c.

📒 Files selected for processing (2)
  • docs/en/configure/networking/how_to/kube_ovn/configure_bgp.mdx
  • docs/en/configure/networking/how_to/kube_ovn/understanding_kube_ovn.mdx

Comment thread docs/en/configure/networking/how_to/kube_ovn/configure_bgp.mdx
@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying alauda-container-platform with  Cloudflare Pages  Cloudflare Pages

Latest commit: 5f86e6c
Status: ✅  Deploy successful!
Preview URL: https://bd9eae48.alauda-container-platform.pages.dev
Branch Preview URL: https://bgp-support.alauda-container-platform.pages.dev

View logs

@oilbeater oilbeater merged commit 7d74be6 into master Apr 17, 2026
3 checks passed
@oilbeater oilbeater deleted the bgp-support branch April 17, 2026 04:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant