-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
2.6->3.0 Upgrades
-
False
-
None
-
False
-
To Do
-
43% To Do, 14% In Progress, 43% Done
This issue covers the migration process from OSSM 2.x (likely 2.5 or 2.6) to OSSM 3.0. This is different from minor release upgrades.
While we will aim to make this as painless as possible, we expect that there will be more work than a minor release upgrade. From customer conversations to date, things that are important for them include:
- Being able to migrate an application while maintaining application traffic (zero-down time from an end user perspective)
- Not having to create a new cluster... it should be possible to have both OSSM 2 and 3 on the same cluster simultaneously. This makes it easier to have traffic load balanced against services in both meshes during the migration.
- is blocked by
-
OSSM-5860 IstioCNI installation fails when running in parallel with 2.x on istio-cni conflicts
-
- New
-
-
-
- Closed
-
- is related to
-
OSSM-6268 Kiali - Seamless upgrade from 2.6 to 3.0
-
- ON_DEV
-
- relates to
-
-
- ON_DEV
-