Skip to content
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

Add support for Cilium CNI #3168

Open
yboaron opened this issue Sep 24, 2024 · 2 comments
Open

Add support for Cilium CNI #3168

yboaron opened this issue Sep 24, 2024 · 2 comments
Labels
cilium cilium CNI enhancement New feature or request help wanted Looking for someone to work on this

Comments

@yboaron
Copy link
Contributor

yboaron commented Sep 24, 2024

What would you like to be added:

I am creating this issue to track Submariner support for Cilium CNI.

Currently, Cilium CNI is recognized as a generic CNI by Submariner, and subctl verify e2e tests seem to fail on clusters with Cilium CNI.

Why is this needed:

Enable multi-cluster networking using Submariner on clusters with Cilium CNI.

Other Info:

In order to support new CNI in Submariner there is a need to update the following functions:

  • CNI network discovery - responsible for pod,service CIDRs and CNI plugin name auto-discovery.
  • Submariner RouteAgent handlers (optional) - used to apply configuration specific for CNI, check Calico ippool handler for example.
@dfarrell07
Copy link
Member

@gk-fschubert agreed to help with this one in #3159 (comment). Thanks! You can assign yourself here (I'd do it, but can't due to GitHub anti-spam restrictions).

@yboaron
Copy link
Contributor Author

yboaron commented Nov 14, 2024

This post covers Submariner deployment on K8S-Kind/Cilium and K8S-Kind/Calico clusters

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cilium cilium CNI enhancement New feature or request help wanted Looking for someone to work on this
Projects
Status: Backlog
Development

No branches or pull requests

2 participants