-
Notifications
You must be signed in to change notification settings - Fork 66
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
OVNKubernetes CNI IC deployment support #2726
Conversation
🤖 Created branch: z_pr2726/aswinsuryan/ovn-ic-cni |
0e3531f
to
376ac21
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor Printf
tweak.
Signed-off-by: Aswin Suryanarayanan <[email protected]>
* Removed SBDB configuration as we are not programming SBDB now will be removed for all the cases once we compltely move to the new implemnetation * Fixed issues in naming Signed-off-by: Aswin Suryanarayanan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to fix compile errors but otherwise looks good.
Signed-off-by: Aswin Suryanarayanan <[email protected]>
🤖 Closed branches: [z_pr2726/aswinsuryan/ovn-ic-cni] |
With OVN IC CNI 3 kind of deployment are possible
1)SIngle Zone (Or in non-ic deployment)
This is similar to the current deployment. Here a OVN Kubernetes db service will be running and it will be passed by submariner-operator to the routeagent/network plugin syncer code.
2)MultiZone and more than one node per zone.
In this case there will be no OVN db service will be present. But there will be an endpoint per zone. Submariner operator will pass the comma separated list of IP Port and protocol and the endpoint name to the route agent and networkpluginsyncer. The pod will chose one of them depending on the zone it is running
3)Multizone , one node per zone.
For this deployment there will be no service or endpoints. Submariner-Operator will pass the value local. The pods needs to use socket connection to program ovn.
Fixes: submariner-io/enhancements#191
This PR also passed the NBDB and SBDB values to the submariner-route agent daemon set as route agent will be now responsible for programming the OVN routes and policies.