[DOCS] Document netkit pod interfaces for Calico CNI (tech preview)#2713
Draft
tomastigera wants to merge 1 commit intotigera:mainfrom
Draft
[DOCS] Document netkit pod interfaces for Calico CNI (tech preview)#2713tomastigera wants to merge 1 commit intotigera:mainfrom
tomastigera wants to merge 1 commit intotigera:mainfrom
Conversation
Adds a section to the eBPF "enabling" page describing how to opt the Calico CNI plugin into creating netkit L2 pairs (Linux 6.7+) instead of veth, via spec.calicoNetwork.linuxPodInterfaceType=Netkit on the operator's Installation. Notes the BPF_NETKIT_PRIMARY perf benefit, the 6.7 kernel prerequisite (with silent veth fallback on older kernels), and the asymmetric revert behavior (existing netkit interfaces stay, but eBPF treats them as veth via TC/TCX). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds documentation to Calico OSS “next” eBPF enablement guide describing how to opt the Calico CNI into using Linux netkit pod interfaces (tech preview) for improved eBPF dataplane performance on Linux 6.7+.
Changes:
- Documented the netkit vs veth behavior and performance motivation for the eBPF data plane.
- Added prerequisites (Linux 6.7+) and operator-based enable/revert procedures via
spec.calicoNetwork.linuxPodInterfaceType.
| ***Procedure*** | ||
|
|
||
| Set `spec.calicoNetwork.linuxPodInterfaceType` to `Netkit` on the operator's `Installation` resource: | ||
|
|
| ***Prerequisites*** | ||
|
|
||
| * Kernel 6.7 or later on every node where you want netkit interfaces. | ||
| Older kernels silently fall back to veth, so it is safe to set the field on heterogeneous clusters — but only nodes on a 6.7+ kernel will see the performance benefit. |
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
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.
Product Version(s):
Calico Open Source (next, master)
Issue:
Companion to projectcalico/calico#12619 (CNI support for
device_type: netkit) and tigera/operator#4767 (operator-sidelinuxPodInterfaceTypefield). Tracked under CORE-10672.Link to docs preview:
Will fill in once the build finishes.
SME review:
DOCS review:
Additional information:
Adds a tech-preview section to
calico/operations/ebpf/enabling-ebpf.mdxdescribing how to opt the Calico CNI plugin into creating netkit L2 pairs (Linux 6.7+) instead of veth, viaspec.calicoNetwork.linuxPodInterfaceType=Netkiton the operatorInstallation. Covers:BPF_NETKIT_PRIMARYinsidendo_start_xmit()for better throughput and tail latency under contention).Notes:
_api.mdxreference is auto-generated from the operator API bycrd-ref-docs, so the newLinuxPodInterfaceTypefield will pick up automatically on the next docs build.calico/operations/ebpf/; the new section is contextually with the eBPF data plane because that is where the perf benefit applies.Merge checklist: