-
Enhancement
-
Resolution: Done
-
Major
-
2.13.0 GA
-
5
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
3
-
API CCS Sprint 37 (3Scale), API CCS Sprint 38 (3Scale), API CCS Sprint 39 (3Scale), API CCS Sprint 40 (3Scale), API CCS Sprint 42 (3Scale), API CCS Sprint 43 (3Scale), API CCS Sprint 44 (3Scale) 2
Use case:
3scale API Manager is deployed using 3scale Operator and uses embedded PostgreSQL database. Move the existing 3scale APIManager from using embedded PostgreSQL to using external PostgreSQL for system and/or zync components.
There are 2 possible migration paths from embedded PostgresSQL to external PostgreSQL .
1. embedded Postgres (10.x) -> External Postgres ( 10.x ) -> External Postgres (13.X)
2. embedded Postgres (10.X) -> External Postgres (13.X)
The reason for the second migration path is that due to business considerations (e.g. cost, standard etc) an external PostgreSQL 10.x cannot be provisioned. However, External PostgreSQL 13.X can or is already provisioned.