Upgrade and migrate Kong Gateway
Before you start
- Back up your data: Back up your Kong Gateway configuration before upgrading so you can restore it if something goes wrong.
- Review breaking changes: Check for breaking changes between your current version and the target version.
- Check version support: Confirm your current and target versions are supported, and identify any required intermediate upgrade stops.
- Review the changelog: Check the full changelog for every release between your current version and the target version.
- Check performance benchmarks: Review benchmark results for your target version to understand performance expectations.
Choose an upgrade strategy
The right strategy depends on your deployment topology and available resources.
|
Deployment type |
Recommended strategy |
|---|---|
| Traditional mode | Dual-cluster upgrade if resources allow; in-place upgrade if constrained |
| Hybrid mode control planes | Dual-cluster upgrade if resources allow; in-place upgrade if constrained |
| Hybrid mode data planes | Rolling upgrade |
| DB-less mode | Rolling upgrade |
| Konnect data plane | Rolling upgrade |
We provide a detailed, in-depth upgrade guide that walks you through the upgrade process for each deployment type, and everything you need to know to prepare for a successful upgrade. Review this guide before you start your upgrade.
flowchart TD
A{Deployment type?} --> B(Traditional mode)
A{Deployment type?} --> C(Hybrid mode)
A{Deployment type?} --> D(DB-less mode)
A{Deployment type?} --> E(Konnect DP)
B ---> F{Enough hardware to
run another cluster?}
C --> G(Upgrade CP first) & H(Upgrade DP second)
D ----> K([Rolling upgrade])
E ----> K
G --> F
F ---Yes--->I([Dual-cluster upgrade])
F ---No--->J([In-place upgrade])
H ---> K
click K "/gateway/upgrade/rolling/"
click I "/gateway/upgrade/dual-cluster/"
click J "/gateway/upgrade/in-place/"
Upgrade Konnect data planes
Konnect data plane upgrades work differently from self-managed upgrades. There are no database migrations. Instead, you provision new nodes and decommission old ones, or let Kong handle it automatically.
LTS version upgrades
3.10 to 3.14 LTS upgrade
Upgrade from Kong Gateway 3.10 LTS to 3.14 LTS.
3.4 to 3.10 LTS upgrade
Upgrade from Kong Gateway 3.4 LTS to 3.10 LTS.
2.8 to 3.4 LTS upgrade
Upgrade from Kong Gateway 2.8 LTS to 3.4 LTS.