Skip to content
|
You are browsing the Kong Gateway documentation archive. This documentation is no longer actively maintained.
See the latest Kong Gateway documentation.
Kong Gateway Enterprise [ARCHIVE]
2.5.x

PermalinkMigrating from Kong Community Gateway to Kong Enterprise

PermalinkMigrating from Kong Community Gateway 2.5.x to Kong Enterprise 2.5.x

As of Kong Gateway version 2.1.x and later, it is no longer necessary to explicitly run the migrate-community-to-enterprise command parameter to to migrate all Kong Gateway entities to Kong Enterprise. 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.

PermalinkPrerequisites

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.5.x, upgrade to Kong 2.5.x before migrating Kong Gateway (OSS) to Kong Gateway 2.5.x.

PermalinkMigration steps

The following steps guide you through the migration process.

  1. Download Kong Gateway 2.5.x and configure it to point to the same datastore as your Kong Gateway (OSS) 2.5.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]

  2. Confirm that all of the entities are now available on your Kong Gateway node.