-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Cilium Support for Azure CNI #4540
Comments
Is |
Might come with a new name but for right now, the team is working on the ePBF specific capability. We're workign on clarifying that Azure CNI Powered by Cilium isuse WITH Azure CNI Overlay and Azure CNI Pod Subnet rather than it's own CNI option. Does that make sense? |
@chasewilson the team is working on the ePBF-specific capability. What is being delivered as part of this deliverable? That is causing more confusion than anything. Is this support for Cilium on Windows, are these eBPF hooks for windows or an all together different CNI offering with Windows using eBPF and not Cilium? |
Good feedback here @amitmavgupta thank you. As of right now this is only Cilium support for Azure CNI Overlay. Not necessarily all ePBF on Windows. Does that make sense? I will Adjust the Title. |
Thanks @chasewilson probably the last query :) is this coming in via native eBPF support on Windows or via some kind of a Linux-offload using DPUs? |
TBH, that's a little outside my scope of control as to what the Windows team is committing to here. My commitment in this is the Cilium implementation for AKS and unfortunately, i'm not sure if Windows is bringing that natively. They could be but I can't provide commitment one way or another. I hope that helps. |
Thanks @chasewilson no worries. |
Public Preview ETA : Q3 2025*
*ETAs are estimations and are subject to change
Description
Azure CNI with the ePBF dataplane (Azure CNI Powered by Cilium) currently only supports Linux. This feature adds ePBF dataplane support to Windows SKUs
Windows Version support to be announced at a later date.
The text was updated successfully, but these errors were encountered: