Skip to content

[cilium] 更新内核要求:4.19+ → 5.10+#786

Open
changluyi wants to merge 1 commit into
alauda:mainfrom
changluyi:docs/cilium-kernel-5.10
Open

[cilium] 更新内核要求:4.19+ → 5.10+#786
changluyi wants to merge 1 commit into
alauda:mainfrom
changluyi:docs/cilium-kernel-5.10

Conversation

@changluyi

@changluyi changluyi commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

变更概述

根据 Cilium 官方文档(requirements-generic),最低内核要求已从 4.19+ 提升至 5.10+

变更内容

  • 中英文版:kernel 4.19+ (5.10+ recommended)kernel 5.10 or later
  • 不支持列表新增 Ubuntu 20.04(未启用 HWE 内核,5.4.x < 5.10)
  • 支持的操作系统补充具体内核版本号
  • 说明 RHEL 8.10 的 4.18 内核等效于 5.10

影响文件

  • docs/en/solutions/How_to_Deploy_Cilium_eBPF_L4_LoadBalancer_with_Source_IP_Preservation.md
  • docs/zh/solutions/How_to_Deploy_Cilium_eBPF_L4_LoadBalancer_with_Source_IP_Preservation.md

Summary by CodeRabbit

Documentation

  • Updated Cilium/eBPF L4 LoadBalancer deployment documentation with revised kernel and OS support requirements. Minimum Linux kernel is now 5.10+, with expanded compatibility matrices clarifying unsupported versions and explicitly listing supported platforms including Ubuntu 22.04, RHEL 8.x, and openEuler 22.03.

@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@changluyi, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 6 minutes and 26 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b9c7459b-1b81-4efc-b187-640f6438bc85

📥 Commits

Reviewing files that changed from the base of the PR and between df7e102 and 51ff687.

📒 Files selected for processing (2)
  • docs/en/solutions/How_to_Deploy_Cilium_eBPF_L4_LoadBalancer_with_Source_IP_Preservation.md
  • docs/zh/solutions/How_to_Deploy_Cilium_eBPF_L4_LoadBalancer_with_Source_IP_Preservation.md

Walkthrough

This PR updates Cilium/eBPF deployment documentation in both English and Chinese versions, clarifying the minimum Linux kernel requirement as 5.10+ and expanding the operating system support matrix with explicit version constraints and equivalence notes for various distributions.

Changes

Cilium/eBPF Compatibility Documentation

Layer / File(s) Summary
Kernel requirement and OS compatibility updates
docs/en/solutions/How_to_Deploy_Cilium_eBPF_L4_LoadBalancer_with_Source_IP_Preservation.md, docs/zh/solutions/How_to_Deploy_Cilium_eBPF_L4_LoadBalancer_with_Source_IP_Preservation.md
Minimum Linux kernel requirement raised to 5.10+. Unsupported OS list expanded to explicitly include Ubuntu 20.04 without HWE and kernel ranges for CentOS/RHEL 7. Supported OS list updated with kernel version specifics: Ubuntu 22.04 (5.15+), RHEL 8.x (4.18+ equivalent to 5.10), and openEuler 22.03 (5.10+).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit hops through kernel land,
Where Linux 5.10 takes its stand,
With Ubuntu, RHEL, and openEuler bright,
The compatibility matrix shines so right! ✨🐰

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically summarizes the main change: updating Cilium kernel requirements from 4.19+ to 5.10+.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@docs/en/solutions/How_to_Deploy_Cilium_eBPF_L4_LoadBalancer_with_Source_IP_Preservation.md`:
- Line 24: Update the RHEL 7.x kernel version string in the docs: replace the
line containing "RHEL 7.x (kernel version 3.10.x - 4.18.x)" with "RHEL 7.x
(kernel version 3.10.x)" in both language versions (the English entry shown and
the corresponding Chinese line), ensuring the kernel range for RHEL 7.x is
changed from "3.10.x - 4.18.x" to just "3.10.x".
- Around line 22-30: Update the kernel requirement wording: keep the general
"Linux kernel 5.10 or later" line but remove the inconsistent range in the
unsupported RHEL 7 entry (replace "RHEL 7.x (kernel 3.10.x - 4.18.x)" with "RHEL
7.x (kernel 3.10.x)"), and clarify RHEL 8 support by changing the supported list
item from "RHEL 8.x (kernel 4.18+ on RHEL 8.10, equivalent to 5.10)" to a
minimum-version form such as "RHEL 8.6+ (kernels with the required backports;
e.g., RHEL 8.10 with 4.18 is considered feature-equivalent to 5.10)" so the doc
references the exact phrases "Linux kernel 5.10 or later", "RHEL 7.x (kernel
3.10.x)", and "RHEL 8.6+" to locate and update the bullets consistently.
🪄 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: af151d6d-df27-4c9a-9efd-b2cacf2c524d

📥 Commits

Reviewing files that changed from the base of the PR and between 0332d44 and df7e102.

📒 Files selected for processing (2)
  • docs/en/solutions/How_to_Deploy_Cilium_eBPF_L4_LoadBalancer_with_Source_IP_Preservation.md
  • docs/zh/solutions/How_to_Deploy_Cilium_eBPF_L4_LoadBalancer_with_Source_IP_Preservation.md

Comment on lines +22 to +30
> **Note**: Cilium/eBPF requires Linux kernel **5.10 or later** (or equivalent, e.g., 4.18 on RHEL 8.10). The following operating systems are **NOT supported**:
> - CentOS 7.x (kernel version 3.10.x)
> - RHEL 7.x (kernel version 3.10.x - 4.18.x)
> - Ubuntu 20.04 with HWE kernel disabled (kernel version 5.4.x)
>
> Supported operating systems:
> - Ubuntu 22.04
> - RHEL 8.x
> - openEuler 22.03
> - Ubuntu 22.04 (kernel 5.15+)
> - RHEL 8.x (kernel 4.18+ on RHEL 8.10, equivalent to 5.10)
> - openEuler 22.03 (kernel 5.10+)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

What are the minimum Linux kernel requirements for Cilium eBPF as documented in the official Cilium documentation?

💡 Result:

According to the official Cilium documentation, the minimum Linux kernel requirement for running a Cilium agent is kernel version 5.10 or later [1][2]. Equivalent versions, such as kernel 4.18 on RHEL 8.10, are also supported [1][2]. While 5.10 is the baseline requirement, the documentation notes that more recent kernels may provide additional eBPF functionality that Cilium will automatically detect and utilize [1][2]. Additionally, specific advanced features may require even newer kernel versions. For example, IPv6 BIG TCP support requires kernel 5.19 or later, while IPv4 BIG TCP support requires kernel 6.3 or later [1][3].

Citations:


🌐 Web query:

Does Cilium documentation confirm that RHEL 8.10 kernel 4.18 is equivalent to kernel 5.10 for eBPF support?

💡 Result:

Yes, the official Cilium documentation explicitly confirms that the kernel 4.18 found on RHEL 8.10 is considered equivalent to kernel 5.10 for the purpose of meeting Cilium's minimum system requirements [1][2][3]. This equivalence exists because Red Hat Enterprise Linux (RHEL) backports necessary eBPF features from newer upstream kernels into its 4.18 kernel, allowing it to satisfy the requirements that Cilium otherwise expects from a standard kernel version 5.10 or later [1][4]. As noted in the documentation, Cilium's agent performs checks on startup; while it generally recommends kernel 5.10 or later, it recognizes RHEL 8.x (specifically 8.6 and above) as having the necessary feature set for functionality [1][4]. Users should be aware that while this equivalence is documented for the minimum core requirements, certain advanced features may still have their own specific minimum kernel version dependencies [1].

Citations:


Fix kernel requirement wording to match Cilium system requirements

  • The “Linux kernel 5.10+” requirement and “RHEL 8.10 kernel 4.18 is equivalent to 5.10” are consistent with Cilium’s official requirements.
  • Update the unsupported entry “RHEL 7.x (kernel 3.10.x - 4.18.x)”: RHEL 7 is 3.10-based, so the “- 4.18.x” portion is internally inconsistent.
  • Clarify the supported RHEL 8 scope: Cilium recognizes RHEL 8.6+ as having the required feature set (so “RHEL 8.x” is too broad without a minimum version).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@docs/en/solutions/How_to_Deploy_Cilium_eBPF_L4_LoadBalancer_with_Source_IP_Preservation.md`
around lines 22 - 30, Update the kernel requirement wording: keep the general
"Linux kernel 5.10 or later" line but remove the inconsistent range in the
unsupported RHEL 7 entry (replace "RHEL 7.x (kernel 3.10.x - 4.18.x)" with "RHEL
7.x (kernel 3.10.x)"), and clarify RHEL 8 support by changing the supported list
item from "RHEL 8.x (kernel 4.18+ on RHEL 8.10, equivalent to 5.10)" to a
minimum-version form such as "RHEL 8.6+ (kernels with the required backports;
e.g., RHEL 8.10 with 4.18 is considered feature-equivalent to 5.10)" so the doc
references the exact phrases "Linux kernel 5.10 or later", "RHEL 7.x (kernel
3.10.x)", and "RHEL 8.6+" to locate and update the bullets consistently.

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