Overview of the Dual-Cluster Upgrade strategy for Kong Gateway
The dual-cluster upgrade strategy involves deploying a new Kong Gateway cluster (Version Y) with its own database alongside the existing cluster (Version X). Traffic is gradually shifted from X to Y using a load balancer. This is the safest upgrade method as it ensures no planned business downtime and allows for immediate rollback by redirecting traffic back to Cluster X.
Applicability:
- Traditional mode deployments.
- Control planes in hybrid mode deployments.
Key Limitations:
- Runtime Metrics: Metrics relying on the database (e.g., request counters in the Rate Limiting Advanced plugin or Vitals buffered metrics) will not be synchronized between the two databases during the transition, leading to inaccurate metrics until the upgrade is complete.