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

Support upgrades to the new OVN IC implementation #193

Assignees
Labels
help wanted Looking for someone to work on this ovn-ic priority:high size:medium

Comments

@aswinsuryan
Copy link
Contributor

aswinsuryan commented Apr 27, 2023

Update should be supported

  • when submariner moves from old implementation to new
  • when Openshift moves from an non-ic to ic version
@aswinsuryan aswinsuryan added size:medium help wanted Looking for someone to work on this labels Apr 27, 2023
@aswinsuryan aswinsuryan moved this to Todo in Submariner 0.16 Apr 27, 2023
@aswinsuryan aswinsuryan self-assigned this May 9, 2023
@aswinsuryan aswinsuryan assigned vthapar and unassigned aswinsuryan Aug 9, 2023
vthapar added a commit to vthapar/submariner that referenced this issue Aug 23, 2023
When a submariner installation upgrades from legacy non-OVN-IC version to
an OVN-IC version, cleanup resources created by legacy installation.

Fixes submariner-io/enhancements#193

Signed-off-by: Vishal Thapar <[email protected]>
vthapar added a commit to vthapar/submariner that referenced this issue Aug 23, 2023
When a submariner installation upgrades from legacy non-OVN-IC version to
an OVN-IC version, cleanup resources created by legacy installation.

Fixes submariner-io/enhancements#193

Signed-off-by: Vishal Thapar <[email protected]>
vthapar added a commit to vthapar/submariner that referenced this issue Aug 23, 2023
When a submariner installation upgrades from legacy non-OVN-IC version to
an OVN-IC version, cleanup resources created by legacy installation.

Fixes submariner-io/enhancements#193

Signed-off-by: Vishal Thapar <[email protected]>
vthapar added a commit to vthapar/submariner that referenced this issue Aug 30, 2023
When a submariner installation upgrades from legacy non-OVN-IC version to
an OVN-IC version, cleanup resources created by legacy installation.

Fixes submariner-io/enhancements#193

Signed-off-by: Vishal Thapar <[email protected]>
@github-project-automation github-project-automation bot moved this from Todo to Done in Submariner 0.16 Aug 30, 2023
@aswinsuryan
Copy link
Contributor Author

More changes needs to be done.

  1. Code will be added to operator to cleanup in case of upgrade from Submariner 0.15 to 0.16
  2. Operator will no longer add ovnnb db connect information to daemonset. Instead routeagents will fetch it form their own nodes by themselves on startup. This will allow rollin upgrade of nodes in a cluster from nonIC to IC. Each routeagent will be able to detect which OVN it is using and operator will not have to track node upgrades.
  3. The expectation is that any cluster undergoing upgrade from OCP <4.14 to 4.14 will be unreachable from other clusters because of possible datapath issues while some nodes are IC and others non IC. Connectivity should be restored once all nodes are IC without any extra effort required from user or submariner.

@aswinsuryan aswinsuryan reopened this Aug 30, 2023
@aswinsuryan aswinsuryan reopened this Aug 30, 2023
novad03 pushed a commit to novad03/k8s-submariner that referenced this issue Nov 25, 2023
When a submariner installation upgrades from legacy non-OVN-IC version to
an OVN-IC version, cleanup resources created by legacy installation.

Fixes submariner-io/enhancements#193

Signed-off-by: Vishal Thapar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment