Migrating from Kong Gateway (OSS) to Kong Gateway
As of Kong Gateway version 2.1.x and later, it is no longer necessary to explicitly
migrate-community-to-enterprise command parameter to to migrate all
Kong Gateway (OSS) entities to Kong Gateway. Running the
kong migrations commands
performs that migration command on your behalf.
Important: You can only migrate to a Kong Gateway version that
supports the same Kong Gateway (OSS) version.
Warning: This action is irreversible, therefore it is strongly
recommended to back up your production data before migrating from
Kong Gateway (OSS) to Kong Gateway.
- If running a version of Kong Gateway (OSS) earlier than 2.6.x,
upgrade to Kong 2.6.x before migrating
Kong Gateway (OSS) to Kong Gateway 2.6.x.
The following steps guide you through the migration process.
Download Kong Gateway 2.6.x and configure it to point to the
same datastore as your Kong Gateway (OSS) 2.6.x node. The migration
command expects the datastore to be up-to-date on any pending migration:
kong migrations up [-c configuration_file]
kong migrations finish [-c configuration_file]
Confirm that all of the entities are now available on your
Kong Gateway node.