Loading...

XML

Word

Printable

Type: Epic
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: Documentation
Labels:
None

Epic Name:
Upgrade path from 3scale 2.x on OCP 3.11 to 3scale 2.x on OCP 4.1
3Scale PT Tested upstream:
Not Started
3scale PT Docs:
Not Started
3scale PT Product Specs:
Not Started
3scale PT Product Update Ready:
Not Started
3scale PT Released In Saas:
Not Started
3scale PT Verified Product:
Not Started
Epic Status:
Done
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Current customers with a template installation on OCP 3.11 would migrate to an operator installation on OCP 4.x on a separate cluster.

The approach would be to do a backup and restore from the primary to the new cluster and achieve a managed switchover.

The 3scale versions must we equal in both environments.

In future this upgrade path must be maintained for new 3scale and OpenShift releases until 3scale on OCP 3.11 is deprecated.

This is the current documentation on backup/restore procedures: https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.6/html/operating_3scale/backup-restore

relates to

THREESCALE-4236 Simple working example of backup and restore for system-postgres & system-oracle

Closed

Assignee:: Unassigned

Reporter:: Mark Cheshire (Inactive)

Tester:: Marian Ganisin (Inactive)

Developer:: Andreu Masferrer

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: 2019/06/28 1:38 PM

Updated:: 2021/10/24 6:10 AM

Resolved:: 2020/09/07 11:19 AM