3scale 2.15 → 2.16 migration¶
This page is version 1.0.0: Kustomize and GitOps, without a Pattern CR. Validated Pattern in the version selector is the newer guide.
This repository is for OpenShift administrators and platform SREs who run 3scale in-cluster and must upgrade from 2.15 to 2.16. Product procedure and supported matrix: Migrating Red Hat 3scale API Management 2.16.
Use it to externalize PostgreSQL (system) and Redis (system and backend) in-cluster before you upgrade the 3scale operator to 2.16. The databases stay on OpenShift. The 3scale operator no longer manages them after you set externalComponents.
A lab cutover typically takes a few hours once the cluster and RWX storage are ready. Production duration depends on database size and the maintenance window.
Lab-validated package
Versions and storage defaults reflect a lab migration — see Tested versions. Reconfirm Supported Configurations and adapt placeholders (REPLACE_*) and StorageClasses to your cluster before you apply manifests.
What you get¶
| Area | Location in the repo |
|---|---|
| Kustomize bases and overlays | kustomize/ |
| Vault chart and External Secrets Subscription | kustomize/overlays/lab-vault* |
| Operational runbooks (clone-friendly) | docs/runbooks/ (ES), docs/runbooks/en/ (EN) |
| OpenShift GitOps / Argo CD | gitops/ |
| RHACM hub patterns | gitops/rhacm/ |
Quick path¶
- Why this repo
- Prerequisites
- Official Red Hat documentation
- Vault and External Secrets
- Migration sequence
- Tested versions
- Day 2 operations (after the cutover)
Command examples on this site assume Linux (bash). For Git Bash on Windows, use docs/runbooks/01-bis-externalize-postgresql-windows.md and docs/runbooks/02-bis-externalize-redis-windows.md in the repository.